unit-test-scheduled-async

To unit test Spring @Async methods, call the method directly and assert the returned CompletableFuture using explicit timeouts. Awaitility can also be applied to wait for async results deterministically without relying on actual thread pools or background executors.

@Scheduled task tests become flaky and slow when depending on real executors, cron triggers, and thread scheduling. You can isolate the scheduling behavior by invoking the scheduled method directly in your JUnit 5 test and verifying mocked dependencies instead of waiting for actual triggers.

The best way to verify dependencies in async tests is using Mockito to mock the called components. After directly invoking the @Async or @Scheduled method and awaiting the CompletableFuture, assert the specific mock invocations to validate execution logic and counts.

Awaitility works with JUnit 5 to validate scheduled task execution timing. It provides deterministic waits and explicit timeouts for asynchronous assertions, ensuring your @Scheduled and CompletableFuture tests do not hang while verifying execution outcomes.

You can test exception handling in asynchronous methods without a thread pool by directly invoking the @Async method in your JUnit 5 test. Awaitility and explicit timeouts capture the async exceptions, while Mockito verifies the mocked dependency interactions triggered by the failure.

To test a cache refresh @Scheduled method without waiting for the cron trigger, call the method directly in your JUnit 5 unit test. Verify the repository interactions using Mockito to ensure the refresh logic executes correctly without relying on actual schedulers.