java-testing-style
Installation
SKILL.md
Java Testing Style
Default Heuristics
- Prefer FIRST: Fast, Isolated, Repeatable, Self-Verifying, and Timely.
- Prefer OTAO: one test covers one behavior and ideally has one reason to fail. Multiple assertions are fine when they verify that same behavior.
- Name unit tests
given{SomeCondition}_should{ExpectedResult}. - Name the observed value
actual. - Use JUnit Jupiter assertions from
org.junit.jupiter.api.Assertions; do not introduce AssertJ unless the project requires it or the user asks for it. - Keep assertions simple and readable.