junit5-testcontainers-patterns

A set of JUnit 5 and Testcontainers patterns for testing Spring Boot applications at the smallest suitable scope. JUnit 5 is a Java testing framework, while Testcontainers runs real services such as databases in temporary containers.

In plain words
What is it for?
Use it when writing or reviewing tests for business logic, controllers, database queries, mappings, caching, security, or complete HTTP flows involving databases or external services.
Why use it?
It helps avoid slow, overly broad tests by choosing between plain unit tests, focused Spring tests, and full integration tests. It also makes each test’s purpose and link to an acceptance criterion explicit.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/loiane/specs-driven-development-spring-angular/junit5-testcontainers-patterns
Any agent
npx skills add loiane/specs-driven-development-spring-angular --skill junit5-testcontainers-patterns
Clone the repo
git clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angular

Made for: Claude Code, Codex.

Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,343 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00050 $0.01343
Opus 5 $0.00025 $0.00672
Sonnet 5 $0.00010 $0.00269
Haiku 4.5 $0.00005 $0.00134

Measured 2d ago against content hash 882073908baf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

junit5-testcontainers-patterns scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/junit5-testcontainers-patterns/SKILL.md · 131 lines

How it starts

The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.

JUnit 5 + Testcontainers patterns

Choose the smallest scope that covers the AC

AC type Use
Pure logic (calculator, validator, mapper) Plain JUnit 5, no Spring
Controller validation, status codes, JSON shape @WebMvcTest
JPA query / mapping @DataJpaTest + Testcontainers (@ServiceConnection)
End-to-end through HTTP, with DB / external @SpringBootTest(webEnvironment = RANDOM_PORT) + Testcontainers
Cache, security filter chain, bean wiring targeted slice (e.g. @WebMvcTest + @Import)

@SpringBootTest is a last resort. If a slice test can cover it, use the slice.

Naming + traceability

  • Every @Test and @ParameterizedTest method MUST carry @DisplayName. No exceptions — write the display name before the test body so articulating it forces clarity about what the test verifies. (Project rule: feedback_displayname_on_every_test.md.)

  • The full annotation block on every test method is all three lines, in this order:

    @Test
    @Tag("AC-007")
    @DisplayName("AC-007: given expired gift card, when applied, then returns 4xx")
    void appliesExpiredGiftCard() { ... }
    
  • Display-name format for AC-traced tests: "<T-ID>: given <precondition>, when <action>, then <outcome>". Short BDD-style sentence is acceptable for utility/regression tests not tied to a specific AC.

  • @Tag("AC-NNN") makes the test machine-readable for the traceability matrix.

  • One AC per test method when feasible.

  • The simplify phase audits every newly-authored or modified test in the diff for @DisplayName — that's the safety net if the red phase missed it.

Testcontainers with @ServiceConnection (Spring Boot 4)

@DataJpaTest
@Testcontainers
class GiftCardRepositoryTest {

    @Container @ServiceConnection
    static PostgreSQLContainer<?> postgres = new PostgreSQLContainer<>("postgres:17-alpine");

    @Autowired GiftCardRepository repo;

    @Test
    @DisplayName("AC-004: given a new gift card, when saved and reloaded, then balance is preserved")
    @Tag("AC-004")
    void persistsBalance() {
        var saved = repo.save(GiftCard.with(BigDecimal.valueOf(100)));
        assertThat(repo.findById(saved.id()).orElseThrow().balance())
            .isEqualByComparingTo("100");
    }
}

Read the full file on GitHub · 131 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 131 lines · 50 tokens per session scan A 882073908baf

Subscribe to this mod's changes

junit5-testcontainers-patterns is a skill published in the GitHub repository loiane/specs-driven-development-spring-angular (58 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 1,343 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

spec-kitty-charter-doctrine

Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…

Priivacy-ai/spec-kitty · 135 tokens

spec-kitty-implement-review

Orchestrate the implement-review loop for Spec Kitty work packages using any configured agent. Covers agent dispatch, state transitions, rejection cycles, arbiter escalation, and dependency-aware sequencing across all 13 supported coding agents. Triggers: "implement and review WPs", "run the implement-review loop"…

Priivacy-ai/spec-kitty · 120 tokens

spec-kitty-mission-review

Review a fully merged Spec Kitty mission post-merge (all WPs done/approved) to verify spec→code fidelity, FR coverage, drift, risks, and security. Triggers: "review the merged mission", "post-merge mission review", "verify the completed mission", "audit the mission implementation", "mission-level acceptance review"…

Priivacy-ai/spec-kitty · 155 tokens

spec-kitty-program-orchestrate

Orchestrate a multi-repo, multi-mission Spec Kitty program end-to-end: run specify → plan → tasks → implement → review → merge → mission-review → post-merge fixes across several repositories in a defined dependency order, using background sub-agents for parallel work and a pulse-heartbeat safety net for long…

Priivacy-ai/spec-kitty · 188 tokens

spec-kitty-runtime-next

Drive the canonical spec-kitty next --mission control loop for mission advancement. Load agent profiles at init, apply action-scoped doctrine context at each step boundary, and pull specific tactics/directives on demand. Triggers: "run the next step", "what should runtime do next", "advance the mission", "what is the…

Priivacy-ai/spec-kitty · 110 tokens

spec-kitty-bulk-edit-classification

Recognize when a mission is a bulk edit and drive the occurrence-classification guardrail on the user's behalf. Triggers: user says any variant of "rename X to Y", "change the terminology", "migrate all occurrences", "replace across the codebase", "the X feature is now the Y feature", "sed everywhere", or any request…

Priivacy-ai/spec-kitty · 157 tokens