Unit Test Scheduled Async

This gives you patterns for unit testing Spring's @Scheduled and @Async methods without waiting for actual cron intervals or thread pool execution. It shows how to call scheduled methods directly (the annotations are ignored in unit tests anyway), use CompletableFuture.get() with timeouts, and leverage Awaitility for race conditions. The examples cover mocking dependencies with Mockito, testing exception propagation through ExecutionException, and verifying execution counts. The honest take: most developers test these wrong by either trying to invoke the Spring proxy or waiting for real scheduling, so having clear examples of calling methods directly and mocking the underlying logic saves a lot of confusion.

skills.sh installs: 3.9K
GitHub stars: 369
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add giuseppe-trisciuoglio/developer-kit --skill unit-test-scheduled-async --agent claude-code

Installs into .claude/skills of the current project.

Files

Unit Testing `@Scheduled` and `@Async` Methods

Overview

Patterns for unit testing Spring @Scheduled and @Async methods with JUnit 5. Test CompletableFuture results, use Awaitility for race conditions, mock scheduled task execution, and validate error handling — without waiting for real scheduling intervals.

When to Use

Testing @Scheduled method logic
Testing @Async method behavior
Verifying CompletableFuture results
Testing async error handling
Testing cron expression logic without waiting for actual scheduling
Validating thread pool behavior and execution counts
Testing background task logic in isolation

Instructions

Call @Async methods directly — bypass Spring's async proxy; the annotation is irrelevant in unit tests
Mock dependencies with @Mock and @InjectMocks (Mockito)
Wait for completion — use CompletableFuture.get(timeout, unit) or await().atMost(...).untilAsserted(...)
Call @Scheduled methods directly — do not wait for cron/fixedRate; the annotation is ignored in unit tests
Test exception paths — verify ExecutionException wrapping on CompletableFuture.get()