java-junit
Get best practices for JUnit 5 unit testing, including data-driven tests
Profile →npx skills add github/awesome-copilot --skill java-junit --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# JUnit 5+ Best Practices Your goal is to help me write effective unit tests with JUnit 5, covering both standard and data-driven testing approaches. ## Project Setup - Use a standard Maven or Gradle project structure. - Place test source code in `src/test/java`. - Include dependencies for `junit-jupiter-api`, `junit-jupiter-engine`, and `junit-jupiter-params` for parameterized tests. - Use build tool commands to run tests: `mvn test` or `gradle test`. ## Test Structure - Test classes should have a `Test` suffix, e.g., `CalculatorTest` for a `Calculator` class. - Use `@Test` for test methods. - Follow the Arrange-Act-Assert (AAA) pattern. - Name tests using a descriptive convention, like `methodName_should_expectedBehavior_when_scenario`. - Use `@BeforeEach` and `@AfterEach` for per-test setup and teardown. - Use `@BeforeAll` and `@AfterAll` for per-class setup and teardown (must be static methods). - Use `@DisplayName` to provide a human-readable name for test classes and methods. ## Standard Tests - Keep tests focused on a single behavior. - Avoid testing multiple conditions in one test method. - Make tests independent and idempotent (can run in any order). - Avoid test interdepe
- Project Setup
- Test Structure
- Standard Tests
- Data-Driven (Parameterized) Tests
- Assertions
- Mocking and Isolation
- Test Organization
What does the java-junit skill do?
Get best practices for JUnit 5 unit testing, including data-driven tests
How do I install it?
Run `npx skills add github/awesome-copilot --skill java-junit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.