+ Start a Discussion
Scott SpilkerScott Spilker 

List has no rows for assignment to SObject - Contact Query

Hello,

I'm new to writing test cases but this seems fairly straight forward.  I am starting with the following test case and am getting a "List has no rows for assignment to SObject" error when running this very simple test case.
 
@isTest
public class ContactChart_Test {  
    
    static testMethod void findContact ()
    {
           Id contId = [Select Id From Contact Limit 1 ].Id; 
           
        }   
}

 
Best Answer chosen by Scott Spilker
SarfarajSarfaraj
Yes it is definitely possible. Use this,
@isTest(SeeAllData=true)
public class ContactChart_Test {  
    
    static testMethod void findContact ()
    {
           Id contId = [Select Id From Contact Limit 1 ].Id; 
           
        }   
}

But usually we create the test data in test class. Read the test data section of the following for the best practices,

https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_testing_data_access.htm
 

All Answers

SarfarajSarfaraj
Hi Scott,

I am not sure what will be your next step after fetching the Contact Id. However this will solve your current error,
@isTest
public class ContactChart_Test {  
    
    static testMethod void findContact ()
    {
           Contact c = new Contact(LastName='Spilker');
           insert c;
           Id contId = [Select Id From Contact Limit 1 ].Id; 
           
        }   
}

Please note that usually you dont access existing data in your org in test class. You create all data that you need.

You can use org data using the seealldata=true annotation, but that has very limited use case.

--Akram
Scott SpilkerScott Spilker
Is is not possible to query for an existing contact rather than creating a new one?
SarfarajSarfaraj
Yes it is definitely possible. Use this,
@isTest(SeeAllData=true)
public class ContactChart_Test {  
    
    static testMethod void findContact ()
    {
           Id contId = [Select Id From Contact Limit 1 ].Id; 
           
        }   
}

But usually we create the test data in test class. Read the test data section of the following for the best practices,

https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_testing_data_access.htm
 
This was selected as the best answer
Scott SpilkerScott Spilker
Thanks.  That helps.  I understand the best practice of creating test data in our test class but I needed to know if there was another way.  
Amit Chaudhary 8Amit Chaudhary 8
Hi Scott Spilker,

I will recommend you to follow below best pratice test classes.
1) Avoid seeAllData= true
2) Add Assert in every method
3) Create your test data in each method.

Please check below post for test classes.
1) http://amitsalesforce.blogspot.in/search/label/Test%20Class
2) http://amitsalesforce.blogspot.in/2015/06/best-practice-for-test-classes-sample.html

Please follow below salesforce Best Practice for Test Classes :-

1. Test class must start with @isTest annotation if class class version is more than 25
2. Test environment support @testVisible , @testSetUp as well
3. Unit test is to test particular piece of code working properly or not .
4. Unit test method takes no argument ,commit no data to database ,send no email ,flagged with testMethod keyword .
5. To deploy to production at-least 75% code coverage is required
6. System.debug statement are not counted as a part of apex code limit.
7. Test method and test classes are not counted as a part of code limit
9. We should not focus on the  percentage of code coverage ,we should make sure that every use case should covered including positive, negative,bulk and single record .
Single Action -To verify that the the single record produces the correct an expected result .
Bulk action -Any apex record trigger ,class or extension must be invoked for 1-200 records .
Positive behavior : Test every expected behavior occurs through every expected permutation , i,e user filled out every correctly data and not go past the limit .
Negative Testcase :-Not to add future date , Not to specify negative amount.
Restricted User :-Test whether a user with restricted access used in your code .
10. Test class should be annotated with @isTest .
11 . @isTest annotation with test method  is equivalent to testMethod keyword .
12. Test method should static and no void return type .
13. Test class and method default access is private ,no matter to add access specifier .
14. classes with @isTest annotation can't be a interface or enum .
15. Test method code can't be invoked by non test request .
16. Stating with salesforce API 28.0 test method can not reside inside non test classes .
17. @Testvisible annotation to make visible private methods inside test classes.
18. Test method can not be used to test web-service call out . Please use call out mock .
19. You can't  send email from test method.
20.User, profile, organization, AsyncApexjob, Corntrigger, RecordType, ApexClass, ApexComponent ,ApexPage we can access without (seeAllData=true) .
21. SeeAllData=true will not work for API 23 version eailer .
22. Accessing static resource test records in test class e,g List<Account> accList=Test.loadData(Account,SobjectType,'ResourceName').
23. Create TestFactory class with @isTest annotation to exclude from organization code size limit .
24. @testSetup to create test records once in a method  and use in every test method in the test class .
25. We can run unit test by using Salesforce Standard UI,Force.com IDE ,Console ,API.
26. Maximum number of test classes run per 24 hour of period is  not grater of 500 or 10 multiplication of test classes of your organization.
27. As apex runs in system mode so the permission and record sharing are not taken into account . So we need to use system.runAs to enforce record sharing .
28. System.runAs will not enforce user permission or field level permission .
29. Every test to runAs count against the total number of DML issued in the process .


Please let us know if this post will help you

Thanks
Amit Chaudhary