specs-driven-development-spring-angular test-code.instructions.md

Rules for writing Java tests with JUnit 5 and Testcontainers, a tool that runs real services such as databases in temporary containers during tests. Each test tied to an acceptance criterion must be traceable to that requirement.

In plain words
What is it for?
Testing code under src/test, including web layers, repositories, database changes, message brokers, and migrations. It covers acceptance-criterion tags, integration-test containers, fixtures, and forbidden shortcuts.
Why use it?
The rules prevent tests from passing for the wrong reasons and keep unit, integration, naming, synchronization, and test-environment practices consistent.

Instructions file for GitHub Copilot

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 instructions/loiane/specs-driven-development-spring-angular/test-code
Clone the repo
git clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angular

Made for: GitHub Copilot.

Per session 356 This file is loaded in full into every session.
When invoked 356 The same file — it is already loaded in full.
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.00356 $0.00356
Opus 5 $0.00178 $0.00178
Sonnet 5 $0.00071 $0.00071
Haiku 4.5 $0.00036 $0.00036

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

Security

Grade A, and why

specs-driven-development-spring-angular test-code.instructions.md 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.

.github/instructions/test-code.instructions.md · 34 lines

What it actually says

Test code guardrails

You are editing test code under src/test/**.

Required

  • Every test method that asserts an AC must have BOTH @Tag("AC-NNN") AND @DisplayName("AC-NNN: <description>").
  • Use the smallest scope that covers the AC: plain JUnit ≺ slice (@WebMvcTest, @DataJpaTest) ≺ @SpringBootTest.
  • When the project declares Testcontainers, integration tests for repositories / DB-touching controllers / migrations / message brokers are mandatory. Use @ServiceConnection (Spring Boot 3+/4 idiom).
  • Pin Testcontainers image tags (postgres:17-alpine, never postgres:latest).

Forbidden

  • @Disabled without a # DisabledReason: <ticket-or-ADR-link> comment on the line above.
  • Removing assertions to make a test pass.
  • Thread.sleep for synchronization (use Awaitility).
  • Hard-coded host ports.
  • Mocking the SUT.
  • Catching Exception and asserting nothing.
  • @MockBean (deprecated — use @MockitoBean in Spring Boot 4).

Naming

  • Unit tests: *Test.java (Surefire).
  • Integration tests: *IT.java (Failsafe + Testcontainers).
  • Fixtures live in src/test/java/.../testsupport/.

Apply shared/skills/junit5-testcontainers-patterns/SKILL.md and shared/skills/requirements-traceability/SKILL.md.

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 · 34 lines · 356 tokens per session scan A 775ea7a0258a

Subscribe to this mod's changes

specs-driven-development-spring-angular test-code.instructions.md is an instructions file published in the GitHub repository loiane/specs-driven-development-spring-angular (57 stars, last pushed 2mo ago), licensed MIT. It adds 356 tokens to every session, about $0.0018 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.