JUnit User Guide

Use this skill when the main deliverable is JUnit test code and the solution should follow the current JUnit User Guide instead of ad hoc conventions. Migration, build setup, and platform troubleshooting are supporting paths used only when they are necessary to get the test code right.

Load the bundled JUnit reference map when you need a quick route from the user request to the right JUnit documentation area, build-tool guidance, or migration rule.

If the user knows the kind of JUnit task they have but not which prompt or asset fits best, load the examples catalog.

When to Use This Skill

• The user asks how to write or update JUnit tests.
• The user wants a failing or missing test turned into a correct Jupiter test.
• The user needs help migrating JUnit 4 code to JUnit Jupiter as part of updating tests.
• The user needs Maven, Gradle, IDE, or console launcher setup because it blocks test authoring.
• The user is dealing with JUnit Platform, Jupiter, or Vintage engine confusion that prevents tests from running.
• The user needs extension-model guidance to implement test fixtures or reusable test behavior.

When Not to Use This Skill