en un clic
junit5-skill
junit5-skill contient 12 skills collectées depuis jovd83, avec une couverture métier par dépôt et des pages de détail sur le site.
Skills dans ce dépôt
Use when Codex needs to create, run, evaluate, debug, correct, modernize, document, or route JUnit 5 tests and related workflows across component, integration, slice, repository, service, regression, smoke, and migration scenarios.
Use when Codex needs to derive JUnit 5 test scenarios from requirements, code, or existing test case definitions such as TDD, BDD, and plain-text specifications.
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.
Use when Codex needs to run JUnit 5 tests through Maven, Gradle, or the Console Launcher, configure CI pipelines, manage tags and reports, or debug environment-specific execution issues.
Use when Codex needs to create, run, debug, evaluate, refactor, or correct JUnit 5 tests across component, integration, slice, repository, service, smoke, or regression scenarios.
Use when Codex needs to analyze a failing JUnit 5 test run, identify the most likely root cause, and produce a developer-focused diagnosis with concrete next fixes.
Use when Codex needs to document JUnit 5 automation code with clear scenario intent, suite purpose, traceability, or maintainable human-readable explanations.
Use when Codex needs to create, review, or debug JUnit 5 extensions, custom annotations, lifecycle callbacks, parameter resolvers, or reusable execution hooks.
Use when Codex needs to help configure IntelliJ IDEA for JUnit 5 development, execution, debugging, and Junie-style workflows in a JVM project.
Use when Codex needs to help configure Visual Studio Code for JUnit 5 development, execution, debugging, and Codex-driven workflows in a JVM project.
Use when Codex needs to migrate tests from JUnit 3 or JUnit 4 to JUnit 5, replace runners and rules, reduce Vintage usage, and preserve behavioral compatibility during modernization.
Use when Codex needs to summarize JUnit 5 test execution results for non-technical stakeholders in clear business-oriented language instead of raw runner output.