Mixing
@testSetup vs DataFactory?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
2
down vote
favorite
When testing, how will @testSetup be preferable than a DataFactory ??
I understand how both works, but I don't see any case where I'd rather use the @testSetup annotation.
I use this datafactory and it works very well...
Thanks.
apex unit-test test-setup
asked 42 mins ago
Alexis MASSON
818
add a comment |Â
up vote
2
down vote
favorite
When testing, how will @testSetup be preferable than a DataFactory ??
I understand how both works, but I don't see any case where I'd rather use the @testSetup annotation.
I use this datafactory and it works very well...
Thanks.
apex unit-test test-setup
asked 42 mins ago
Alexis MASSON
818
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
When testing, how will @testSetup be preferable than a DataFactory ??
I understand how both works, but I don't see any case where I'd rather use the @testSetup annotation.
I use this datafactory and it works very well...
Thanks.
apex unit-test test-setup
asked 42 mins ago
Alexis MASSON
818
When testing, how will @testSetup be preferable than a DataFactory ??
I understand how both works, but I don't see any case where I'd rather use the @testSetup annotation.
I use this datafactory and it works very well...
Thanks.
apex unit-test test-setup
apex unit-test test-setup
asked 42 mins ago
Alexis MASSON
818
asked 42 mins ago
Alexis MASSON
818
asked 42 mins ago
Alexis MASSON
818
asked 42 mins ago
Alexis MASSON
818
asked 42 mins ago
Alexis MASSON
818
818
add a comment |Â
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
2
down vote
A major reason to use @TestSetup is the situation where you have many tests that require the same baseline of data. The @TestSetup method runs once and all its data is available to all the test methods in the class. Any changes made by a test method are rolled back but the @TestSetup data isn't. The benefit is faster test running because the baseline data inserts are only done once per test class not once per test method.
A downside is that the only way to get references to the data created in @TestSetup is to query for it. But those queries are much cheaper than the inserts.
I use @TestSetup sometimes, and other times, when I want to refer to the test data in the following asserts, use builder classes invoked from each test method so I have references to the test objects without having to do queries.
You can choose to use whatever technique you like to create the SObjects and use that method inside the @TestStup method or outside of it.
answered 15 mins ago
Keith C
90.9k1082186
add a comment |Â
up vote
2
down vote
I use both. Why would you have to choose one over the other? @testSetup is a way to reduce test execution time by reusing the data created once in all the test methods of a test class.
TestFactory is to reuse same data in multiple test classes.
Ex:
@isTest
private class AvinashTest
@testSetup
static void testSetup()
Test.startTest();
Account a = (Account) TestFactory.createSObject(new Account(), true);
a.Oracle_Cust_Number__c = '10';
update a;
Brand__c b = (Brand__c) TestFactory.createSObject(new Brand__c(), true);
example_Product__c rocProd = TestDataFactory.getexampleProduct( 'Test Prod', b );
insert rocProd;
Contact c = (Contact) TestFactory.createSObject(new Contact(), true);
Opportunity o = (Opportunity) TestFactory.createSObject(new Opportunity(AccountId=a.Id,StageName='Closed Lost', Channel_Type__c = 'Direct'), true);
Product2 prod1 = (Product2) TestFactory.createSObject(new Product2(Brand__c=b.Id), true);
prod1.example_Product__c = rocProd.Id;
update new User(Service_Provider__c = true, Id = UserInfo.getUserId());
Test.stopTest();
answered 12 mins ago
Avinash
1,0631619
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
A major reason to use @TestSetup is the situation where you have many tests that require the same baseline of data. The @TestSetup method runs once and all its data is available to all the test methods in the class. Any changes made by a test method are rolled back but the @TestSetup data isn't. The benefit is faster test running because the baseline data inserts are only done once per test class not once per test method.
A downside is that the only way to get references to the data created in @TestSetup is to query for it. But those queries are much cheaper than the inserts.
I use @TestSetup sometimes, and other times, when I want to refer to the test data in the following asserts, use builder classes invoked from each test method so I have references to the test objects without having to do queries.
You can choose to use whatever technique you like to create the SObjects and use that method inside the @TestStup method or outside of it.
answered 15 mins ago
Keith C
90.9k1082186
add a comment |Â
up vote
2
down vote
A major reason to use @TestSetup is the situation where you have many tests that require the same baseline of data. The @TestSetup method runs once and all its data is available to all the test methods in the class. Any changes made by a test method are rolled back but the @TestSetup data isn't. The benefit is faster test running because the baseline data inserts are only done once per test class not once per test method.
A downside is that the only way to get references to the data created in @TestSetup is to query for it. But those queries are much cheaper than the inserts.
I use @TestSetup sometimes, and other times, when I want to refer to the test data in the following asserts, use builder classes invoked from each test method so I have references to the test objects without having to do queries.
You can choose to use whatever technique you like to create the SObjects and use that method inside the @TestStup method or outside of it.
answered 15 mins ago
Keith C
90.9k1082186
add a comment |Â
up vote
2
down vote
up vote
2
down vote
A major reason to use @TestSetup is the situation where you have many tests that require the same baseline of data. The @TestSetup method runs once and all its data is available to all the test methods in the class. Any changes made by a test method are rolled back but the @TestSetup data isn't. The benefit is faster test running because the baseline data inserts are only done once per test class not once per test method.
A downside is that the only way to get references to the data created in @TestSetup is to query for it. But those queries are much cheaper than the inserts.
I use @TestSetup sometimes, and other times, when I want to refer to the test data in the following asserts, use builder classes invoked from each test method so I have references to the test objects without having to do queries.
You can choose to use whatever technique you like to create the SObjects and use that method inside the @TestStup method or outside of it.
answered 15 mins ago
Keith C
90.9k1082186
A major reason to use @TestSetup is the situation where you have many tests that require the same baseline of data. The @TestSetup method runs once and all its data is available to all the test methods in the class. Any changes made by a test method are rolled back but the @TestSetup data isn't. The benefit is faster test running because the baseline data inserts are only done once per test class not once per test method.
A downside is that the only way to get references to the data created in @TestSetup is to query for it. But those queries are much cheaper than the inserts.
I use @TestSetup sometimes, and other times, when I want to refer to the test data in the following asserts, use builder classes invoked from each test method so I have references to the test objects without having to do queries.
You can choose to use whatever technique you like to create the SObjects and use that method inside the @TestStup method or outside of it.
answered 15 mins ago
Keith C
90.9k1082186
answered 15 mins ago
Keith C
90.9k1082186
answered 15 mins ago
Keith C
90.9k1082186
answered 15 mins ago
Keith C
90.9k1082186
90.9k1082186
add a comment |Â
add a comment |Â
up vote
2
down vote
I use both. Why would you have to choose one over the other? @testSetup is a way to reduce test execution time by reusing the data created once in all the test methods of a test class.
TestFactory is to reuse same data in multiple test classes.
Ex:
@isTest
private class AvinashTest
@testSetup
static void testSetup()
Test.startTest();
Account a = (Account) TestFactory.createSObject(new Account(), true);
a.Oracle_Cust_Number__c = '10';
update a;
Brand__c b = (Brand__c) TestFactory.createSObject(new Brand__c(), true);
example_Product__c rocProd = TestDataFactory.getexampleProduct( 'Test Prod', b );
insert rocProd;
Contact c = (Contact) TestFactory.createSObject(new Contact(), true);
Opportunity o = (Opportunity) TestFactory.createSObject(new Opportunity(AccountId=a.Id,StageName='Closed Lost', Channel_Type__c = 'Direct'), true);
Product2 prod1 = (Product2) TestFactory.createSObject(new Product2(Brand__c=b.Id), true);
prod1.example_Product__c = rocProd.Id;
update new User(Service_Provider__c = true, Id = UserInfo.getUserId());
Test.stopTest();
answered 12 mins ago
Avinash
1,0631619
add a comment |Â
up vote
2
down vote
I use both. Why would you have to choose one over the other? @testSetup is a way to reduce test execution time by reusing the data created once in all the test methods of a test class.
TestFactory is to reuse same data in multiple test classes.
Ex:
@isTest
private class AvinashTest
@testSetup
static void testSetup()
Test.startTest();
Account a = (Account) TestFactory.createSObject(new Account(), true);
a.Oracle_Cust_Number__c = '10';
update a;
Brand__c b = (Brand__c) TestFactory.createSObject(new Brand__c(), true);
example_Product__c rocProd = TestDataFactory.getexampleProduct( 'Test Prod', b );
insert rocProd;
Contact c = (Contact) TestFactory.createSObject(new Contact(), true);
Opportunity o = (Opportunity) TestFactory.createSObject(new Opportunity(AccountId=a.Id,StageName='Closed Lost', Channel_Type__c = 'Direct'), true);
Product2 prod1 = (Product2) TestFactory.createSObject(new Product2(Brand__c=b.Id), true);
prod1.example_Product__c = rocProd.Id;
update new User(Service_Provider__c = true, Id = UserInfo.getUserId());
Test.stopTest();
answered 12 mins ago
Avinash
1,0631619
add a comment |Â
up vote
2
down vote
up vote
2
down vote
I use both. Why would you have to choose one over the other? @testSetup is a way to reduce test execution time by reusing the data created once in all the test methods of a test class.
TestFactory is to reuse same data in multiple test classes.
Ex:
@isTest
private class AvinashTest
@testSetup
static void testSetup()
Test.startTest();
Account a = (Account) TestFactory.createSObject(new Account(), true);
a.Oracle_Cust_Number__c = '10';
update a;
Brand__c b = (Brand__c) TestFactory.createSObject(new Brand__c(), true);
example_Product__c rocProd = TestDataFactory.getexampleProduct( 'Test Prod', b );
insert rocProd;
Contact c = (Contact) TestFactory.createSObject(new Contact(), true);
Opportunity o = (Opportunity) TestFactory.createSObject(new Opportunity(AccountId=a.Id,StageName='Closed Lost', Channel_Type__c = 'Direct'), true);
Product2 prod1 = (Product2) TestFactory.createSObject(new Product2(Brand__c=b.Id), true);
prod1.example_Product__c = rocProd.Id;
update new User(Service_Provider__c = true, Id = UserInfo.getUserId());
Test.stopTest();
answered 12 mins ago
Avinash
1,0631619
I use both. Why would you have to choose one over the other? @testSetup is a way to reduce test execution time by reusing the data created once in all the test methods of a test class.
TestFactory is to reuse same data in multiple test classes.
Ex:
@isTest
private class AvinashTest
@testSetup
static void testSetup()
Test.startTest();
Account a = (Account) TestFactory.createSObject(new Account(), true);
a.Oracle_Cust_Number__c = '10';
update a;
Brand__c b = (Brand__c) TestFactory.createSObject(new Brand__c(), true);
example_Product__c rocProd = TestDataFactory.getexampleProduct( 'Test Prod', b );
insert rocProd;
Contact c = (Contact) TestFactory.createSObject(new Contact(), true);
Opportunity o = (Opportunity) TestFactory.createSObject(new Opportunity(AccountId=a.Id,StageName='Closed Lost', Channel_Type__c = 'Direct'), true);
Product2 prod1 = (Product2) TestFactory.createSObject(new Product2(Brand__c=b.Id), true);
prod1.example_Product__c = rocProd.Id;
update new User(Service_Provider__c = true, Id = UserInfo.getUserId());
Test.stopTest();
answered 12 mins ago
Avinash
1,0631619
answered 12 mins ago
Avinash
1,0631619
answered 12 mins ago
Avinash
1,0631619
answered 12 mins ago
Avinash
1,0631619
1,0631619
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f233111%2ftestsetup-vs-datafactory%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password