Test Class for Trigger before insert before update
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
1
down vote
favorite
I am very new to APEX and I have written the following trigger that updates the due date on a case based upon an SLA value stored in another object once the user fills a value in a lookup field
trigger SetCaseSLA on Case (before insert, before update)
for (Case ca : Trigger.new)
if ((ca.CaseType__c != NULL) && (ca.DueDate__c == NULL))
id CaseTypeId = ca.CaseType__c;
List<CaseType__c> results = [select SLA__c from caseType_c where id = :CaseTypeId];
Integer mySLA = Integer.valueOf(results[0].get('SLA__c'));
ca.DueDate__c = BusinessHours.add(ca.BusinessHoursId, System.now(), mySLA * 60 * 60 * 1000L);
Then I have written the following Apex Test Class however it would appear that the DueDate is always null and the trigger is not firing is there something wrong with the setup of the test class causing the trigger not to fire?
@isTest
private class TestSetDueDate
@isTest static void TestDueDate()
CaseType__c csecat = new CaseType__c();
csecat.CaseTypeName__c = 'My Type Test';
csecat.SLA__c = 2;
insert csecat;
Case cse = new Case();
cse.Origin='Email';
cse.BusinessHoursID = '01m3C00000008d2QAA';
Test.startTest();
insert cse;
cse.CaseType__c = csecat.id;
update cse;
Test.stopTest();
System.debug(csecat.SLA__c);
System.debug(cse.DueDate__c);
System.debug(cse.CaseType__c);
System.assertEquals(cse.DueDate__c , BusinessHours.add(cse.BusinessHoursId, system.now(), 2 * 60 * 60 * 1000L));
apex trigger failing-tests
add a comment |
up vote
1
down vote
favorite
I am very new to APEX and I have written the following trigger that updates the due date on a case based upon an SLA value stored in another object once the user fills a value in a lookup field
trigger SetCaseSLA on Case (before insert, before update)
for (Case ca : Trigger.new)
if ((ca.CaseType__c != NULL) && (ca.DueDate__c == NULL))
id CaseTypeId = ca.CaseType__c;
List<CaseType__c> results = [select SLA__c from caseType_c where id = :CaseTypeId];
Integer mySLA = Integer.valueOf(results[0].get('SLA__c'));
ca.DueDate__c = BusinessHours.add(ca.BusinessHoursId, System.now(), mySLA * 60 * 60 * 1000L);
Then I have written the following Apex Test Class however it would appear that the DueDate is always null and the trigger is not firing is there something wrong with the setup of the test class causing the trigger not to fire?
@isTest
private class TestSetDueDate
@isTest static void TestDueDate()
CaseType__c csecat = new CaseType__c();
csecat.CaseTypeName__c = 'My Type Test';
csecat.SLA__c = 2;
insert csecat;
Case cse = new Case();
cse.Origin='Email';
cse.BusinessHoursID = '01m3C00000008d2QAA';
Test.startTest();
insert cse;
cse.CaseType__c = csecat.id;
update cse;
Test.stopTest();
System.debug(csecat.SLA__c);
System.debug(cse.DueDate__c);
System.debug(cse.CaseType__c);
System.assertEquals(cse.DueDate__c , BusinessHours.add(cse.BusinessHoursId, system.now(), 2 * 60 * 60 * 1000L));
apex trigger failing-tests
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am very new to APEX and I have written the following trigger that updates the due date on a case based upon an SLA value stored in another object once the user fills a value in a lookup field
trigger SetCaseSLA on Case (before insert, before update)
for (Case ca : Trigger.new)
if ((ca.CaseType__c != NULL) && (ca.DueDate__c == NULL))
id CaseTypeId = ca.CaseType__c;
List<CaseType__c> results = [select SLA__c from caseType_c where id = :CaseTypeId];
Integer mySLA = Integer.valueOf(results[0].get('SLA__c'));
ca.DueDate__c = BusinessHours.add(ca.BusinessHoursId, System.now(), mySLA * 60 * 60 * 1000L);
Then I have written the following Apex Test Class however it would appear that the DueDate is always null and the trigger is not firing is there something wrong with the setup of the test class causing the trigger not to fire?
@isTest
private class TestSetDueDate
@isTest static void TestDueDate()
CaseType__c csecat = new CaseType__c();
csecat.CaseTypeName__c = 'My Type Test';
csecat.SLA__c = 2;
insert csecat;
Case cse = new Case();
cse.Origin='Email';
cse.BusinessHoursID = '01m3C00000008d2QAA';
Test.startTest();
insert cse;
cse.CaseType__c = csecat.id;
update cse;
Test.stopTest();
System.debug(csecat.SLA__c);
System.debug(cse.DueDate__c);
System.debug(cse.CaseType__c);
System.assertEquals(cse.DueDate__c , BusinessHours.add(cse.BusinessHoursId, system.now(), 2 * 60 * 60 * 1000L));
apex trigger failing-tests
I am very new to APEX and I have written the following trigger that updates the due date on a case based upon an SLA value stored in another object once the user fills a value in a lookup field
trigger SetCaseSLA on Case (before insert, before update)
for (Case ca : Trigger.new)
if ((ca.CaseType__c != NULL) && (ca.DueDate__c == NULL))
id CaseTypeId = ca.CaseType__c;
List<CaseType__c> results = [select SLA__c from caseType_c where id = :CaseTypeId];
Integer mySLA = Integer.valueOf(results[0].get('SLA__c'));
ca.DueDate__c = BusinessHours.add(ca.BusinessHoursId, System.now(), mySLA * 60 * 60 * 1000L);
Then I have written the following Apex Test Class however it would appear that the DueDate is always null and the trigger is not firing is there something wrong with the setup of the test class causing the trigger not to fire?
@isTest
private class TestSetDueDate
@isTest static void TestDueDate()
CaseType__c csecat = new CaseType__c();
csecat.CaseTypeName__c = 'My Type Test';
csecat.SLA__c = 2;
insert csecat;
Case cse = new Case();
cse.Origin='Email';
cse.BusinessHoursID = '01m3C00000008d2QAA';
Test.startTest();
insert cse;
cse.CaseType__c = csecat.id;
update cse;
Test.stopTest();
System.debug(csecat.SLA__c);
System.debug(cse.DueDate__c);
System.debug(cse.CaseType__c);
System.assertEquals(cse.DueDate__c , BusinessHours.add(cse.BusinessHoursId, system.now(), 2 * 60 * 60 * 1000L));
apex trigger failing-tests
apex trigger failing-tests
edited Nov 19 at 23:44
David Reed
26k51645
26k51645
asked Nov 19 at 23:43
user3456401
102
102
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
3
down vote
accepted
As in all other Apex functionality, you must query fields that you wish to update on your sObject variables. The only field that is automatically updated for you is Id
after an insert
DML.
After Test.stopTest()
, you must do
cse = [SELECT CaseType__c, DueDate__c FROM Case WHERE Id = :cse.Id];
Only then can you perform assertions to validate your code's behavior.
Thanks @David for your explanation that is exactly where I was going wrong and it really helped me to understand why its necessary
– user3456401
Nov 19 at 23:59
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
As in all other Apex functionality, you must query fields that you wish to update on your sObject variables. The only field that is automatically updated for you is Id
after an insert
DML.
After Test.stopTest()
, you must do
cse = [SELECT CaseType__c, DueDate__c FROM Case WHERE Id = :cse.Id];
Only then can you perform assertions to validate your code's behavior.
Thanks @David for your explanation that is exactly where I was going wrong and it really helped me to understand why its necessary
– user3456401
Nov 19 at 23:59
add a comment |
up vote
3
down vote
accepted
As in all other Apex functionality, you must query fields that you wish to update on your sObject variables. The only field that is automatically updated for you is Id
after an insert
DML.
After Test.stopTest()
, you must do
cse = [SELECT CaseType__c, DueDate__c FROM Case WHERE Id = :cse.Id];
Only then can you perform assertions to validate your code's behavior.
Thanks @David for your explanation that is exactly where I was going wrong and it really helped me to understand why its necessary
– user3456401
Nov 19 at 23:59
add a comment |
up vote
3
down vote
accepted
up vote
3
down vote
accepted
As in all other Apex functionality, you must query fields that you wish to update on your sObject variables. The only field that is automatically updated for you is Id
after an insert
DML.
After Test.stopTest()
, you must do
cse = [SELECT CaseType__c, DueDate__c FROM Case WHERE Id = :cse.Id];
Only then can you perform assertions to validate your code's behavior.
As in all other Apex functionality, you must query fields that you wish to update on your sObject variables. The only field that is automatically updated for you is Id
after an insert
DML.
After Test.stopTest()
, you must do
cse = [SELECT CaseType__c, DueDate__c FROM Case WHERE Id = :cse.Id];
Only then can you perform assertions to validate your code's behavior.
answered Nov 19 at 23:49
David Reed
26k51645
26k51645
Thanks @David for your explanation that is exactly where I was going wrong and it really helped me to understand why its necessary
– user3456401
Nov 19 at 23:59
add a comment |
Thanks @David for your explanation that is exactly where I was going wrong and it really helped me to understand why its necessary
– user3456401
Nov 19 at 23:59
Thanks @David for your explanation that is exactly where I was going wrong and it really helped me to understand why its necessary
– user3456401
Nov 19 at 23:59
Thanks @David for your explanation that is exactly where I was going wrong and it really helped me to understand why its necessary
– user3456401
Nov 19 at 23:59
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
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f239907%2ftest-class-for-trigger-before-insert-before-update%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown