Architecture
JUnit 5 skill pack for creating, debugging, modernizing, documenting, and routing JVM test workflows.
npx -y skills add jovd83/junit5-skill --skill architectureAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when Codex needs to shape or refactor JUnit 5 suite architecture, test package structure, naming, fixture ownership, reuse patterns, or boundaries between component, integration, and service tests.
SKILL.md
1.9 KB, as published. Nobody here has run it
JUnit 5 Architecture
1. Inspect Before Restructuring
- Inspect current package layout, test naming, build filters, and fixture reuse.
- Inspect whether the repo already separates fast and slow tests by tag, source set, or naming convention.
- Read references/suite-shape.md before moving files or changing naming conventions.
2. Choose Stable Boundaries
- Separate component, slice, integration, and service tests intentionally.
- Keep reusable setup close to its owning layer.
- Prefer builders, helpers, and local fixtures before introducing global abstractions.
- Use extensions only when reuse is real and cross-cutting.
3. Refactor for Clarity
- Group tests by behavior or domain concept, not by incidental helper reuse.
- Keep naming consistent with build-tool discovery.
- Avoid base-class pyramids and magical test inheritance.
4. Troubleshooting
- Problem: Shared fixtures leak across unrelated suites. Fix: Push fixtures down to the owning package or convert them to explicit helpers.
- Problem: Test names and package layout hide runtime cost. Fix: Separate slow integration or service suites clearly by tag or naming.