Skip to content

fix: stop the 5-minute schedule test failing on a minute rollover #76

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Mateusz7410 merged 1 commit into from
Nov 6, 2026
Merged

fix: stop the 5-minute schedule test failing on a minute rollover #76

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions force-app/main/default/classes/AsyncTest.cls
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -882,6 +882,8 @@ private class AsyncTest implements Database.Batchable<SObject> {

@IsTest
static void shouldScheduleBatchJobIn5Minutes() {
Datetime beforeScheduling = System.now();

Test.startTest();
Async.batchable(new AsyncTest())
.scopeSize(100)
Expand All @@ -897,9 +899,12 @@ private class AsyncTest implements Database.Batchable<SObject> {
WHERE CronJobDetail.Name = :TEST_SCHEDULABLE_JOB_NAME
];
Assert.areEqual(1, triggers.size(), 'Should have one trigger scheduled.');
Assert.areEqual(
triggers[0].CreatedDate.addMinutes(5).minute(),
triggers[0].NextFireTime.minute(),
Set<Integer> minutesFiveFromScheduling = new Set<Integer>{
beforeScheduling.addMinutes(5).minute(),
triggers[0].CreatedDate.addMinutes(5).minute()
};
Assert.isTrue(
minutesFiveFromScheduling.contains(triggers[0].NextFireTime.minute()),
'Next fire time should be in 5 minutes.'
);
}
Expand Down
Loading