You need to sign in to do that
Don't have an account?
Claire Sunderland
I need to build an Apex Class based on the following Trigger. I have never written an Apex Class and did not write the trigger. I am new to all this. I want it to delete any task that is status 'Completed' and subject 'Callback'.
trigger DeleteCompletedCallbackTaskTrigger on Task (after update) {
for (Task task: Trigger.new) {
if(task.status == 'Completed' && task.subject == 'Callback') {
delete Task;
}
}
}
for (Task task: Trigger.new) {
if(task.status == 'Completed' && task.subject == 'Callback') {
delete Task;
}
}
}
I will recommend you to start using trailhead to learn about test classes
1) https://trailhead.salesforce.com/modules/apex_testing
Also please check below post
1) https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_qs_test.htm
2) https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_testing_example.htm
Pleasse check below post sample test class
1) http://amitsalesforce.blogspot.com/2015/06/best-practice-for-test-classes-sample.html
You write a test class for this the same way that you would any other:
- Set up some data for the controller to access (Account, Contact etc)
- Execute a method/methods:- search
- Verify the behaviour with asserts.
Please update your Batch job like below
Your test class should be like below
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
All Answers
You need to delete perticuler task or all taks where stauts == completed and subject == callback.please tell me.
Thanks
Hemant
1) http://amitsalesforce.blogspot.com/2015/06/trigger-best-practices-sample-trigger.html
Create Apex class like below Trigger should be like below
Let us know if this will help you
I think according to your requirment you need a batch which executes every night and delete all task where status and subject are according to your requirement.
For Example: Let me know if it not solve your problem.
If This helps you please mark it solved.
Thanks
Hemant
Any specific reason why you want to accomplish this as a Trigger. If this is just a cleanup activity to delete all the Completed Tasks with a specific Subject, I would recommend writing a batch job that runs daily at a specific time and deletes all the qualifyign tasks. If you have a specific reason which mandates you to use a trigger, you can use the code specified by Amit, only that it needs a minor update as shown below.
@Amit, The only thing I want to modify in the specified Apex Trigger code is to use the newTask List variable within your for loop or not pass it at all since Trigger context variables are available throughout the execution context.
Please do not forget to mark this thread as SOLVED and answer as the BEST ANSWER if this answer helps address your issue.
@isTest
private class TestDeleteAllCompletedCallbackTask {
//-- Tests DeleteAllCompletedCallbackTask.class.isbatch
static testMethod void validateDeleteAllCompletedCallbackTask(){
is delete Task ; delete Task (Status = 'Completed', Subject = 'Callback')
//Insert new task
insert Task;
new task (Status = 'Open', Subject = 'Callback')
//Update task
update Task;
task = (Status = 'Completed', Subject = 'Callback')
//Delete task
delete Task;
task = (Status = 'Completed', Subject = 'Callback')
Please try below code. And Please mark it solved.
Thanks
Hemant
I will recommend you to start using trailhead to learn about test classes
1) https://trailhead.salesforce.com/modules/apex_testing
Also please check below post
1) https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_qs_test.htm
2) https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_testing_example.htm
Pleasse check below post sample test class
1) http://amitsalesforce.blogspot.com/2015/06/best-practice-for-test-classes-sample.html
You write a test class for this the same way that you would any other:
- Set up some data for the controller to access (Account, Contact etc)
- Execute a method/methods:- search
- Verify the behaviour with asserts.
Please update your Batch job like below
Your test class should be like below
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
I had made mistake in batch.
Try below And Test CLass is Same as Above.
And please dont forgot to Marked as solved.
Thanks
Hemant
Trailhead is the best way to get your self started and become mroe handson with Apex coding and custom development. You can try the Developer - Beginner trail to get started and then progress through the Intermediate and Advanced Levels as you progress and become more comfortable.
1) http://amitsalesforce.blogspot.com/2017/07/how-to-write-test-class-for-scheduler.html
Try below code