You need to sign in to do that
Don't have an account?
![ying liu ying liu](https://dfc-org-production.my.site.com/img/userprofile/default_profile_45_v2.png)
@testsetup will work in all test classes?
Hi,
Document says:
Methods defined with the @testSetup annotation are used for creating common test records that are available for all test methods in the class.
I am confused that the class means all test classes in org or only the test class which contains @testSetup if I run all test classes.
I didn't find the details.
Anyone can explain this to me?
Thanks.
Ying
Document says:
Methods defined with the @testSetup annotation are used for creating common test records that are available for all test methods in the class.
I am confused that the class means all test classes in org or only the test class which contains @testSetup if I run all test classes.
I didn't find the details.
Anyone can explain this to me?
Thanks.
Ying
@testsetup only created data only for a particular test class not for every test class in org.
You can find some good details here-
http://amitsalesforce.blogspot.in/2015/05/testsetup-set-up-test-data-for-entire.html
@testSetup ( Set Up Test Data for an Entire Test Class )Use test setup methods (methods that are annotated with @testSetup) to create test records once and then access them in every test method in the test class. Test setup methods can be time-saving when you need to create reference or prerequisite data for all test methods, or a common set of records that all test methods operate on.
Test setup methods can reduce test execution times especially when you’re working with many records. Test setup methods enable you to create common test data easily and efficiently. By setting up records once for the class, you don’t need to re-create records for each test method. Also, because the rollback of records that are created during test setup happens at the end of the execution of the entire class, the number of records that are rolled back is reduced. As a result, system resources are used more efficiently compared to creating those records and having them rolled back for each test method
NOTE:-
Test setup methods are supported only with the default data isolation mode for a test class. If the test class or a test method has access to organization data by using the @isTest(SeeAllData=true) annotation, test setup methods aren’t supported in this class. Because data isolation for tests is available for API versions 24.0 and later, test setup methods are also available for those versions only.
You can have only one test setup method per test class.
If a fatal error occurs during the execution of a test setup method, such as an exception that’s caused by a DML operation or an assertion failure, the entire test class fails, and no further tests in the class are executed.
If a test setup method calls a non-test method of another class, no code coverage is calculated for the non-test method.
Kindly mark my solution as the best answer if it helps you.
Regards
Mukesh