You need to sign in to do that
Don't have an account?
Steve Cairney
Faking a record ID for a test class
Hi all, when you have a test class in your sandbox that references the ID of a record of a custom object within the sandbox, how to do get round the fact that this object and record won't exist in your production org when you come to test the changeset?
Use the id of inserted record, instead of hardcoding it.
All Answers
I think you are using SeeAllData=true attribute in your test classes. It is generally not a good practice to query the data which is already present in the org. Do not use SeeAllData=true. Instead create the test data in the test class itself and then use that data to test your methods.
I'll work on creating the test data in the class, and report back, thanks.
Please check below post for test classes. I hope that will help you
1) http://amitsalesforce.blogspot.com/search/label/Test%20Class
2) http://amitsalesforce.blogspot.com/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 do let me know if it helps you.
Regards,
Mahesh
Here's the test class as it stands (it's for a webservice)
What I'll need to do is create test data for an object called Its_Approved_Booking__c but I'm not sure how to implement the code in here. I've successfully created a controller and test class using this object but the methods don't work in this class (I've commented out my efforts)
I am not sure what you mean by below line :
You cannot pass the id parameter will creating the record. You need just pass the mandatory fields present on object and then insert the record. Salesforce will generate the id by itself. Something like below should work for you.
Let me know if you have any questions. Thanks.
What's the syntax to take that into account?
Try this code sample then, it should work. Thanks.
Here is the GetBookingDetails from the referenced class, I'm not sure what to put as the string now, since we can't hard-code an ID.
Use the id of inserted record, instead of hardcoding it.
I thought this might solve the issue but the variable bookingdetails is outside the loop now. Can you suggest the correct syntax here?
Enclose you DML operation within Test.startTest() and Test.stopMethod()
The offending is this in the ItsApprovedWebServices.cls
I'm trying various approaches in test class, but nothing is working
This is my latest attempt
How can I ensure that I create the test data for the IA_Product__c but then make sure the list is not empty?