unit-test-scheduled-async SKILL.md skillA
unit-test-scheduled-async from giuseppe-trisciuoglio/developer-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add giuseppe-trisciuoglio/developer-kit/unit-test-scheduled-async@git:20260324.a02e282Pins git:20260324.a02e282 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- giuseppe-trisciuoglio/developer-kit
- Path
plugins/developer-kit-java/skills/unit-test-scheduled-async/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260324.a02e282, committed Mar 24, 2026
- First version recorded
- Feb 7, 2026
- Size
- 5,851 bytes
- Repository stars
- 367
- License
- MIT
Provides patterns for unit testing Spring `@Scheduled` and `@Async` methods using JUnit 5, CompletableFuture, Awaitility, and Mockito. Covers mocking task execution and timing, verifying execution counts, testing cron expressions, validating retry behavior, and simulating thread pool behavior. Use when testing background tasks, cron jobs, periodic execution, scheduled tasks, or thread pool behavior.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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 1. **Call `@Async` methods directly** — bypass Spring's async proxy; the annotation is irrelevant in unit tests 2. **Mock dependencies** with `@Mock` and `@InjectMocks` (Mockito) 3. **Wait for completion** — use `CompletableFuture.get(timeout, unit)` or `await().atMost(...).untilAsserted(...)` 4. **Call `@Scheduled` methods directly** — do not wait for cron/fixedRate; the annotation is ignored in unit tests 5. **Test exception paths** — verify `ExecutionException` wrapping on `CompletableFuture.get()` …
Read the whole file at its exact version.
How to install
mdr add giuseppe-trisciuoglio/developer-kit/unit-test-scheduled-async@sha256:912db37c2216971bThe line at the top of this page pins the label git:20260324.a02e282, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_qabtbq2tsw25ipvy)
6 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Feb 7, 2026 and Mar 24, 2026, about one every 11 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260324.a02e282 latest | 2026-03-24 | a02e282 | 5,851 B | A | view · diff |
| git:20260316.91dc3c4 | 2026-03-16 | 91dc3c4 | 13,214 B | A | view · diff |
| git:20260223.c6d4db1 | 2026-02-23 | c6d4db1 | 13,172 B | A | view · diff |
| v1.0.1 | 2026-02-08 | 147afce | 13,271 B | A | view · diff |
| v1.0.1 | 2026-02-07 | 1a732c7 | 11,482 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5851 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
giuseppe-trisciuoglio/developer-kit · 367 stars · license MIT · pushed 2026-09-10 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qabtbq2tsw25ipvy GET https://markdownregistry.com/api/v1/resolve?ref=giuseppe-trisciuoglio/developer-kit/unit-test-scheduled-async GET https://markdownregistry.com/api/v1/blob/912db37c2216971b2a81bc415bab41f9629f31bf4c0e896b3c20a11de3617070
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.