Apex Code Development You need to sign in to do that
Don't have an account?
SFDC Noob 1 Test class for Batch apex
I have this batch apex sharing recalculation i created with the help of the apex workbook, How can i create a test class for this? The example in the workbook doesn't help me with my situation.
thanks
global class PartnerSharingClass implements Database.Batchable<sObject> {
static String emailAddress = 'test@test.com';
global Database.QueryLocator start(Database.BatchableContext BC){
return Database.getQueryLocator([SELECT Id, Partner__c FROM Opportunity]);
}
global void execute(Database.BatchableContext BC, List<sObject> scope) {
Map<Id, Opportunity> oppMap = new Map<Id, Opportunity>((List<Opportunity>)scope);
List<opportunityshare> newOppShare = new List<OpportunityShare>();
List<OpportunityShare> oldOppShare = [SELECT Id FROM OpportunityShare WHERE Id IN :oppMap.keyset()];
for(Opportunity o : oppMap.Values()){
OpportunityShare pShare = new OpportunityShare();
pshare.UserOrGroupId = o.Partner__c;
pshare.OpportunityAccessLevel = 'Read';
pshare.OpportunityId = o.Id;
newOppShare.add(pshare);
}
try {
Delete oldOppShare;
Database.SaveResult[] lsr = Database.insert(newOppShare,false);
for(Database.Saveresult sr : lsr) {
if(!sr.isSuccess()){
Database.Error err = sr.getErrors()[0];
if(!(err.getStatusCode() == StatusCode.FIELD_FILTER_VALIDATION_EXCEPTION
&& err.getMessage().contains('AccessLevel'))){
Messaging.SingleEmailMessage mail = new Messaging.SingleEmailMessage();
String[] toAddresses = new String[] {emailAddress};
mail.setToAddresses(toAddresses);
mail.setSubject('Apex Sharing Recalculation Exception');
mail.setPlainTextBOdy(
'The Apex Sharing recalculation threw the following exception: ' + err.getMessage());
Messaging.sendEmail(new Messaging.SingleEmailMessage[] {mail});
}
}
}
}catch(DMLException e) {
Messaging.SingleEmailMessage mail = new Messaging.SingleEmailMessage();
String[] toAddresses = new String[] {emailAddress};
mail.setToAddresses(toAddresses);
mail.setSubject('APex Sharing Recalculation Exception');
mail.setPlainTextBody( 'The APex sharing recalculation threw the following exception: ' + e.getMessage());
}
} global void finish(Database.BatchableContext BC) {
Messaging.SingleEmailMessage mail = new Messaging.SingleEmailMessage();
String[] toAddresses = new String[] {emailAddress};
mail.setToAddresses(toAddresses);
mail.setSubject('Apex Sharing Recalculation Completed.');
mail.setPlainTextBody('The Apex sharing recalculation finished processing');
Messaging.sendEmail(new Messaging.SingleEmailMessage[] {mail} );
}
}
thanks
public with sharing class Test_PartnerSharingClass { /** * You'll need to setup test data. * In your case this would be opportunity records * and opportunity share records. **/ @TestSetup static void setupData() { List<Account> accounts = new List<Account>(); List<Opportunity> opps = new List<Opportunity>(); // since this is a batch class, each batch could // handle up to 200 records so best to test that // volume for(Integer i = 0; i < 200; i++) { Account a = new Account(Name = 'Test Account ' + i); accounts.add(a); } insert accounts; for(Integer i = 0; i < 200; i++) { Opportunity o = new Opportunity(Name = 'Test Opp ' + i, StageName = 'Closed Won', CloseDate = System.today(), AccountId = accounts.get(i).Id, Partner__c = // Add a valid value here); opps.add(o); } insert opps; // Now you have 200 opportunities to test. } /** * You have a few code paths, so test each one with a different method. * This method would test a successful sharing recalculation * **/ static testmethod void testOne() { Test.startTest(); PartnerSharingClass batch = new PartnerSharingClass(); Database.executeBatch(batch); Test.stopTest(); // since batch apex is async, this will force it to stop before executing further method lines. // ensure that 200 OpportunityShare records were created Integer numShares = [select count() from OpportunityShare]; System.assertEquals(200, numShares); } /** * Test the portion of code that handles SaveResult errors * **/ static testmethod void testTwo() { // manipulate your data as needed to force save result errors. // for example for(Opportunity o : [select Id from Opportunity]) { // insert some value that would cause the error } Test.startTest(); PartnerSharingClass batch = new PartnerSharingClass(); Database.executeBatch(batch); Test.stopTest(); } /** * Test the exception handling in your try-catch block. * **/ static testmethod void testThree() { // do something to force your code into the catch block. // for example for(Opportunity o : [select Id from Opportunity]) { // insert some value that would cause the exception } Test.startTest(); PartnerSharingClass batch = new PartnerSharingClass(); Database.executeBatch(batch); Test.stopTest(); } }Without knowing your configuration (custom fields, validation rules, etc) it's hard to give an exact test class, but I've added comments that should help.
~ Clint
@isTest public class PartnerSharingClassTest { static testMethod void testMethod1() { Account testAcct = new Account (Name = 'My Test Account'); insert testAcct; Opportunity oppt = new Opportunity(Name ='New mAWS Deal', AccountID = testAcct.ID, StageName = 'Customer Won', Amount = 3000, CloseDate = System.today() ) insert oppt; Opportunity mAWSUsage = new Opportunity( Name = 'mAWS Usage', AccountId = testAcct.Id, StageName = 'Negotiations', CloseDate = System.today(), Original_Source__c = 'Customer', Amount = 555888555); insert mAWSUsage; Test.StartTest(); Database.executeBatch(new PartnerSharingClass(),200 ); Test.StopTest(); } }Please check below blog for test classess. I hope that will help uhttp://amitsalesforce.blogspot.in/search/label/Test%20Class
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
You'll need to build out testTwo() and testThree() to force the code into those lines.
For example, your lines 30-45 handle errors that occur when saving the new OpportunityShare records. You'll need to do something to those records to force them to error when saving.