Testing scheduled apex: CronTrigger does NOT fire after Test.stopTest()

Question

EDIT for clarification of title:

CronTrigger is probably actually firing at some point in the testing process - what is wierd is that CronTrigger.TimesTriggered is NOT incrementing after Test.stopTest()

Any asynchronous calls made within the Test.startTest() and Test.stopTest() methods of a test class should execute upon hitting Test.stopTest().

So, presumably, if I schedule a class using System.schedule(), the CronTrigger object representing that scheduled job should fire immediately upon Test.stopTest(), regardless of CronTrigger.NextFireTime's value.

Here is my schedulable class:

global class Schedulable_Nightly implements Schedulable {

    //PREDEFINED_SCHEDULE = "Every day at midnight"
    public static String PREDEFINED_SCHEDULE = '0 0 0 * * ?';

   global void execute(SchedulableContext SC) {
      Database.executeBatch(new ContractTimelineBatch());
   }
}

And here is my test method, pretty much lifted from SF documentation:

private class TestContractTimelineBatch {           

    @isTest static void test_schedulable(){

       Test.startTest();

          // Schedule the test job
          String jobId = System.schedule('testBasicScheduledApex',
          Schedulable_Nightly.PREDEFINED_SCHEDULE, 
             new Schedulable_Nightly());

          // Get the information from the CronTrigger API object
          CronTrigger ct = [SELECT Id, CronExpression, CronJobDetailId, CronJobDetail.Name, TimesTriggered, PreviousFireTime, NextFireTime, State
             FROM CronTrigger WHERE id = :jobId];

          // Verify the job has not run
          System.assertEquals(0, ct.TimesTriggered);

       Test.stopTest();

       ct = [SELECT Id, CronJobDetailID, TimesTriggered, PreviousFireTime, NextFireTime, State
         FROM CronTrigger WHERE id = :jobid];

       //DEBUG STATEMENT SHOWS THAT ct.TimesTriggered IS STILL 0
       system.debug('Cron - post: ' + ct);

       // Verify that the job has now run   
       System.assertEquals(1, ct.TimesTriggered);

    }

}

This final assertEquals fails because ct.TimesTriggered stays at 0, both before and after Test.stopTest

What gives?

Answer 1

You could take a different approach to your test method

Instead of asserting whether the schedulable class was, in fact, executed, you should be asserting whether the schedulable's execute() method actually did anything and what you expected. Testing that SFDC can schedule/execute a schedulable per its CronTrigger proves nothing - as SFDC is guaranteed to execute your code at or around the time specified in the CronTrigger.

In your case, whether the batch job processed the mocked sobjects is the interesting thing to test.

Answer 2

As of 16-August-2018 this appears to be an issue. Note the following apex test method.

@isTest static void myTestMethod() {

    System.Test.StartTest();
        String jobId = System.schedule(xxx, xxx, xxx);
    System.Test.StopTest();

    //Assertion failed. Expected "Finished" actual "Waiting"
    System.assertEquals('Finished', [select State from CronTrigger where Id = :jobId ][0].State);
}

Answer 3

You need to query for the CronTrigger record for the scheduled job again after test.stopTest() to get the up-to-date value for TimesTriggered. Same as any other object you use a SOQL query to get.

Answer 4

same happened to me and I had to create a schedule class that class a batch class, and then create the respective test classes

Test.start();
Database.executeBatch(new UserActivationJob_JCS());
Test.stopTest();
//assert the logic

Test.startTest();
String jobId = System.schedule('TestScheduledApex', '0 0 0 3 9 ? 2022', new UserActivationJobSchedule_JCS());
Test.stopTest();

//assert the batch will run

Answer 5

you have to remove the @isTest from your method; otherwise, the changes inside your batch will not be committed. Of course, when the test ends, the rollback is done automatically:

static void test_schedulable(){ ... }

you should not use testmethod in this case as well.