Queueable Apex is similar to @future methods. It is an asynchronous apex method. It allows you to submit jobs for asynchronous processing with some additional benefits comparing to @future methods.
Benefits :
- Queueable apex supports non-primitives like SObject and custom Apex types.
- We can monitor the status and progress of Queueable method using the returned Id of AsyncApexJob.
- We can chain one job to another by starting the second job from a running job.
Limitations :
- It shares limits of async Apex & Governor Limits.
- In a single transaction you can add maximum 50 jobs in the queue.
- While chaining jobs, only one child job can exist for each parent job.
Below example is taken from the Queueable Apex trailhead, the purpose of this is just to share a example of Queueable Apex with test class.
Requirements
Create an Queueable Apex class that inserts Contacts for Accounts.
Create a Queueable Apex class that inserts the same Contact for each Account for a specific state. Write unit tests that achieve 100% code coverage for the class.
- Create an Apex class called 'AddPrimaryContact' that implements the Queueable interface.
- Create a constructor for the class that accepts as its first argument a Contact sObject and a second argument as a string for the State abbreviation.
- The execute method must query for a maximum of 200 Accounts with the BillingState specified by the State abbreviation passed into the constructor and insert the Contact sObject record associated to each Account. Look at the sObject clone() method.
- Create an Apex test class called 'AddPrimaryContactTest'.
- In the test class, insert 50 Account records for BillingState "NY" and 50 Account records for BillingState "CA". Create an instance of the AddPrimaryContact class, enqueue the job and assert that a Contact record was inserted for each of the 50 Accounts with the BillingState of "CA".
- The unit tests must cover all lines of code included in the AddPrimaryContact class, resulting in 100% code coverage.
- Run your test class at least once (via 'Run All' tests the Developer Console) before attempting to verify this challenge.
Solution
AddPrimaryContact
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 | public class AddPrimaryContact implements Queueable { Private Contact c; Private String s; public AddPrimaryContact(Contact con, String state){ this.c = con; this.s = state; } public void execute(QueueableContext context) { List<Account> accList = [SELECT ID, Name ,(Select id,FirstName,LastName from contacts ) FROM ACCOUNT WHERE BillingState = :s LIMIT 200 ]; List<Contact> conList=new List<Contact>(); for(Account a: accList){ Contact cont = c.clone(false,false,false,false); cont.AccountId = a.Id; conList.add(cont); } if(conList.size() >0 ) { insert conList; } } } |
AddPrimaryContactTest
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 | @isTest public class AddPrimaryContactTest { @isTest static void TestList() { List<Account> accList = new List <Account>(); for(Integer i=0;i<50;i++) { accList.add(new Account(BillingState = 'CA', name = 'Acc'+i)); } for(Integer j=0;j<50;j++) { accList.add(new Account(BillingState = 'NY', name = 'Acc'+j)); } insert accList; Contact con = new Contact(); con.LastName ='Test'; insert con; String state = 'CA'; AddPrimaryContact apc = new AddPrimaryContact(con, state); Test.startTest(); System.enqueueJob(apc); Test.stopTest(); } } |
If you have any question please leave a comment below.
If you would like to add something to this post please leave a comment below.
Share this blog with your friends if you find it helpful somehow !
Thanks
Keep Coding
0 Comments