What is Testing Async Apex?<\/h2>\n\n\n\n
Testing Async Apex is writing tests for code that Salesforce runs in the background, after the current transaction. You queue the job between Test.startTest and Test.stopTest. When stopTest runs, Salesforce runs every job queued since startTest, right away and in order. Then your asserts check the results.<\/p>\n\n\n\n
Think of a dry cleaner who says “ready tomorrow”. You cannot check the shirt today. Test.stopTest is like a magic button that says “finish all orders now”. So you can check the shirt before you leave the shop.<\/p>\n\n\n\n
Why Testing Async Apex Matters<\/h2>\n\n\n\n
Background jobs fail silently if nobody tests them. Here is why Testing Async Apex matters at Bright Path Tutors.<\/p>\n\n\n\n
- \n
- First, a Queueable job updates unpaid enrolments when a course fee changes.<\/li>\n\n
- Also, a nightly Batch job raises fees by 5% across thousands of courses.<\/li>\n\n
- Next, a trigger calls a future method that sends data to another system.<\/li>\n\n
- Without stopTest, none of these jobs would run before your asserts.<\/li>\n\n
- Finally, async code still needs coverage before you can deploy it.<\/li>\n<\/ul>\n\n\n\n
So every async class needs a test that forces it to run.<\/p>\n\n\n\n
How Testing Async Apex Works<\/h2>\n\n\n\n
Testing Async Apex follows a fixed pattern. First, create test data outside the start and stop block. Next, call Test.startTest, which gives the following code a fresh set of governor limits. Then queue the job, for example with System.enqueueJob or Database.executeBatch. After that, Test.stopTest runs every queued job synchronously. Finally, query the records and assert the results.<\/p>\n\n\n\n
![\"Testing](\"https:\/\/swapnilzambare.com\/blog\/wp-content\/uploads\/2026\/11\/testing-async-apex-starttest-stoptest-diagram-1-1024x640.png\")
How stopTest runs queued jobs before your asserts.<\/figcaption><\/figure>\n\n\n\n Test.startTest<\/h3>\n\n\n\n
Test.startTest marks the start of the code you are really testing. Code after it gets its own set of governor limits. So setup DML does not eat into the limits of the code under test.<\/p>\n\n\n\n
Test.stopTest<\/h3>\n\n\n\n
Test.stopTest ends that block. It runs all async work queued since startTest, then returns. After it, limits go back to the original context.<\/p>\n\n\n\n
Once per Test Method<\/h3>\n\n\n\n
You can call startTest and stopTest only once in each test method. So keep setup before startTest and asserts after stopTest.<\/p>\n\n\n\n
Batch Apex in Tests<\/h3>\n\n\n\n
A test can run only one execute call of a batch job. So insert no more records than the batch size, such as 200, when you test a batch.<\/p>\n\n\n\n
Chained Jobs<\/h3>\n\n\n\n
You cannot chain Queueable jobs in a test. If a job enqueues another job, skip the chain in tests or test each job on its own.<\/p>\n\n\n\n
Async Types and How to Test Them<\/h2>\n\n\n\n
The table below shows how to start each async type inside a test.<\/p>\n\n\n\n
Async type<\/th> Start it with<\/th> Runs at<\/th><\/tr><\/thead> Future method<\/td> Call the @future method<\/td> Test.stopTest<\/td><\/tr> Queueable<\/td> System.enqueueJob(job)<\/td> Test.stopTest<\/td><\/tr> Batch Apex<\/td> Database.executeBatch(batch, 200)<\/td> Test.stopTest, one execute only<\/td><\/tr> Scheduled Apex<\/td> System.schedule(name, cron, job)<\/td> Test.stopTest<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Without vs With startTest and stopTest<\/h2>\n\n\n\n
The table below compares an async test with and without the start and stop block.<\/p>\n\n\n\n
Feature<\/th> Without start and stop<\/th> With start and stop<\/th><\/tr><\/thead> Async job runs before asserts<\/td> No<\/td> Yes, at stopTest<\/td><\/tr> Governor limits<\/td> Shared with setup code<\/td> Fresh set for tested code<\/td><\/tr> Assert sees<\/td> Old values<\/td> Job results<\/td><\/tr> Calls allowed per method<\/td> Not used<\/td> Once each<\/td><\/tr> Best for<\/td> Plain synchronous code<\/td> Async code and limit checks<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n When to use which is simple. Always use startTest and stopTest for async code. Also use them for synchronous code when you want to measure its limits without the setup noise.<\/p>\n\n\n\n
![\"Testing](\"https:\/\/swapnilzambare.com\/blog\/wp-content\/uploads\/2026\/11\/testing-async-apex-starttest-stoptest-diagram-2-1024x640.png\")
Without vs with startTest and stopTest.<\/figcaption><\/figure>\n\n\n\n A Real Testing Async Apex Example<\/h2>\n\n\n\n
Let’s apply Testing Async Apex to two jobs at Bright Path Tutors.<\/p>\n\n\n\n
Step 1: The Queueable Job<\/h3>\n\n\n\n
public with sharing class EnrolmentFeeSyncJob implements Queueable {\n\n private Set<Id> courseIds;\n\n public EnrolmentFeeSyncJob(Set<Id> courseIds) {\n this.courseIds = courseIds;\n }\n\n public void execute(QueueableContext ctx) {\n Map<Id, Course__c> courses = new Map<Id, Course__c>(\n [SELECT Id, Fee__c FROM Course__c WHERE Id IN :courseIds]);\n List<Enrolment__c> rows = [SELECT Id, Course__c FROM Enrolment__c\n WHERE Course__c IN :courseIds AND Is_Paid__c = false];\n for (Enrolment__c e : rows) {\n e.Amount_Due__c = courses.get(e.Course__c).Fee__c;\n }\n update rows;\n }\n}<\/code><\/pre>\n\n\n\nThe job loads the new fees, finds unpaid enrolments for those courses, and copies the fee into Amount_Due__c. Paid enrolments stay as they are.<\/p>\n\n\n\n
Step 2: Test the Queueable<\/h3>\n\n\n\n
@isTest\nstatic void syncsUnpaidEnrolments() {\n Course__c c = TestDataFactory.createCourses(1, true)[0];\n Contact s = TestDataFactory.createStudents(1, true)[0];\n insert new Enrolment__c(Course__c = c.Id, Student__c = s.Id,\n Status__c = 'Active', Is_Paid__c = false);\n c.Fee__c = 6000;\n update c;\n\n Test.startTest();\n System.enqueueJob(new EnrolmentFeeSyncJob(new Set<Id>{ c.Id }));\n Test.stopTest();\n\n Enrolment__c e = [SELECT Amount_Due__c FROM Enrolment__c LIMIT 1];\n Assert.areEqual(6000, e.Amount_Due__c, 'Unpaid enrolment should get the new fee');\n}<\/code><\/pre>\n\n\n\nAll setup happens before startTest. Then the job is queued, and stopTest runs it at once. So the assert sees the updated Amount_Due__c of 6,000.<\/p>\n\n\n\n
Step 3: Test a Batch Job<\/h3>\n\n\n\n
@isTest\nstatic void raisesFeesByFivePercent() {\n TestDataFactory.createCourses(200, true); \/\/ each fee is 5000\n\n Test.startTest();\n Database.executeBatch(new CourseFeeIncreaseBatch(), 200);\n Test.stopTest();\n\n for (Course__c c : [SELECT Fee__c FROM Course__c]) {\n Assert.areEqual(5250, c.Fee__c, 'Fee should rise by 5%');\n }\n}<\/code><\/pre>\n\n\n\nCourseFeeIncreaseBatch multiplies each fee by 1.05 in its execute method. The test inserts exactly 200 courses, which fits in one execute call. Then the loop checks every fee.<\/p>\n\n\n\n
Step 4: Read the Results<\/h3>\n\n\n\n
Here is a simplified view of the test run.<\/p>\n\n\n\n
CourseJobsTest.syncsUnpaidEnrolments Pass\nCourseJobsTest.raisesFeesByFivePercent Pass\nCode coverage: EnrolmentFeeSyncJob 100%, CourseFeeIncreaseBatch 100%<\/code><\/pre>\n\n\n\nBoth jobs ran inside the test. So Testing Async Apex this way proves real results, not just coverage.<\/p>\n\n\n\n
Testing Async Apex for Scheduled Jobs<\/h2>\n\n\n\n
A scheduled job is started with System.schedule and a cron expression. Before stopTest, you can query CronTrigger with the returned job Id to assert the cron expression and next run time. After stopTest, the job has run, so you can assert its effects.<\/p>\n\n\n\n
Common Mistakes with Testing Async Apex<\/h2>\n\n\n\n
- \n
- Queuing a job without Test.stopTest, then asserting before it runs.<\/li>\n\n
- Putting setup DML between startTest and stopTest, which mixes up limits.<\/li>\n\n
- Inserting more than 200 records for a batch test.<\/li>\n\n
- Calling startTest twice in one test method.<\/li>\n\n
- Testing a chain of Queueable jobs in one test.<\/li>\n<\/ul>\n\n\n\n
Best Practices for Testing Async Apex<\/h2>\n\n\n\n
- \n
- Keep setup before startTest and asserts after stopTest.<\/li>\n\n
- Test each async class in its own test method.<\/li>\n\n
- Match batch test data to one batch size.<\/li>\n\n
- Assert both the main result and records that must not change.<\/li>\n\n
- Check limits with the Limits class between startTest and stopTest when needed.<\/li>\n<\/ul>\n\n\n\n
Practice Task<\/h2>\n\n\n\n
Add a test that checks paid enrolments keep their old Amount_Due__c after EnrolmentFeeSyncJob runs. Hint: insert one paid and one unpaid enrolment, then assert both values after stopTest.<\/p>\n\n\n\n
Most Asked Interview Questions on Testing Async Apex<\/h2>\n\n\n\n
Async testing questions appear in most mid-level interviews. Here are the 21 questions asked most about Testing Async Apex.<\/p>\n\n\n\n
Basic Questions on Testing Async Apex<\/h3>\n\n\n\n
Q1: What does Test.startTest do?<\/strong><\/p>\n\n\n\n
It marks the start of the tested code and gives it a fresh set of governor limits.<\/p>\n\n\n\n
Q2: What does Test.stopTest do?<\/strong><\/p>\n\n\n\n
It runs all async work queued since startTest, then restores the original limits.<\/p>\n\n\n\n
Q3: How many times can you call startTest in a test method?<\/strong><\/p>\n\n\n\n
Once.<\/p>\n\n\n\n
Q4: Do future methods run in tests?<\/strong><\/p>\n\n\n\n
Yes, when you call them between startTest and stopTest. They run at stopTest.<\/p>\n\n\n\n
Q5: How do you test a Queueable job?<\/strong><\/p>\n\n\n\n
Call System.enqueueJob between startTest and stopTest, then assert after stopTest.<\/p>\n\n\n\n
Q6: How do you test Batch Apex?<\/strong><\/p>\n\n\n\n
Call Database.executeBatch between startTest and stopTest with no more records than one batch.<\/p>\n\n\n\n
Q7: Why put setup before startTest?<\/strong><\/p>\n\n\n\n
So setup DML and queries do not use the limits of the code you are testing.<\/p>\n\n\n\n
Code and Scenario Questions on Testing Async Apex<\/h3>\n\n\n\n
Q8: Why does my async job not run in the test?<\/strong><\/p>\n\n\n\n
Usually because Test.stopTest is missing, or the job was queued before startTest.<\/p>\n\n\n\n
Q9: How many batch execute calls can run in a test?<\/strong><\/p>\n\n\n\n
Only one, so keep the test data within one batch size.<\/p>\n\n\n\n
Q10: Can you chain Queueable jobs in a test?<\/strong><\/p>\n\n\n\n
No. Test each job separately, or skip the chain when Test.isRunningTest is true.<\/p>\n\n\n\n
Q11: How do you test a scheduled job?<\/strong><\/p>\n\n\n\n
Call System.schedule between startTest and stopTest, check CronTrigger, then assert results after stopTest.<\/p>\n\n\n\n
Q12: How do you test a trigger that calls a future method?<\/strong><\/p>\n\n\n\n
Run the DML between startTest and stopTest, then assert after stopTest.<\/p>\n\n\n\n
Q13: How do you check governor limits in a test?<\/strong><\/p>\n\n\n\n
Read Limits.getQueries and similar methods inside the start and stop block, then assert them.<\/p>\n\n\n\n
Q14: Where should asserts go in an async test?<\/strong><\/p>\n\n\n\n
After Test.stopTest, so they see the finished job results.<\/p>\n\n\n\n
Advanced Questions on Testing Async Apex<\/h3>\n\n\n\n
Q15: Why use startTest and stopTest even for synchronous code?<\/strong><\/p>\n\n\n\n
To measure the limits of the tested code on their own, without setup noise.<\/p>\n\n\n\n
Q16: How do you test the finish method of a batch?<\/strong><\/p>\n\n\n\n
Run the batch in the start and stop block, then assert the finish method’s effects, such as a log record.<\/p>\n\n\n\n
Q17: How do you test a callout made from a Queueable?<\/strong><\/p>\n\n\n\n
Set a callout mock with Test.setMock before enqueuing the job.<\/p>\n\n\n\n
Q18: How do you get the job Id of a Queueable in a test?<\/strong><\/p>\n\n\n\n
System.enqueueJob returns it. Then you can query AsyncApexJob for its status.<\/p>\n\n\n\n
Q19: What happens to records created by the async job?<\/strong><\/p>\n\n\n\n
They are rolled back with all other test data when the test ends.<\/p>\n\n\n\n
Q20: How do you test a Database.Stateful batch?<\/strong><\/p>\n\n\n\n
Run it once in the test, then assert the totals it writes in finish.<\/p>\n\n\n\n
Q21: What is a common pattern for long Queueable chains?<\/strong><\/p>\n\n\n\n
Test each job’s execute logic on its own and guard the next enqueue with Test.isRunningTest.<\/p>\n\n\n\n
Official Resources<\/h2>\n\n\n\n