Junit 5 Skill
sickn33/agentic-awesome-skills
Generates production-grade JUnit 5 unit and integration tests in Java.
A skill your agent uses when writing tests for Java (Quarkus or Spring) code - JUnit Jupiter structure, Mockito for collaborators, test slices, Testcontainers, and framework-native integration…
$ npx skills add makifbaysal/tasktrooper --skill java-testing-junit-mockito -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install makifbaysal/tasktrooper java-testing-junit-mockito --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/makifbaysal/tasktrooper.git skills-src && mkdir -p .claude/skills && cp -r skills-src/catalog/agents/backend-developer/skills/java-testing-junit-mockito .claude/skills/java-testing-junit-mockito && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "java-testing-junit-mockito" agent skill from https://github.com/makifbaysal/tasktrooper/tree/main/catalog/agents/backend-developer/skills/java-testing-junit-mockito into .claude/skills/java-testing-junit-mockito/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "java-testing-junit-mockito", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/makifbaysal/tasktrooper/tree/main/catalog/agents/backend-developer/skills/java-testing-junit-mockitoType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add makifbaysal/tasktrooper --skill java-testing-junit-mockito -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install makifbaysal/tasktrooper java-testing-junit-mockito --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/makifbaysal/tasktrooper.git skills-src && mkdir -p .agents/skills && cp -r skills-src/catalog/agents/backend-developer/skills/java-testing-junit-mockito .agents/skills/java-testing-junit-mockito && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "java-testing-junit-mockito" agent skill from https://github.com/makifbaysal/tasktrooper/tree/main/catalog/agents/backend-developer/skills/java-testing-junit-mockito into .agents/skills/java-testing-junit-mockito/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "java-testing-junit-mockito", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add makifbaysal/tasktrooper --skill java-testing-junit-mockito -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install makifbaysal/tasktrooper java-testing-junit-mockito --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/makifbaysal/tasktrooper.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/catalog/agents/backend-developer/skills/java-testing-junit-mockito .cursor/skills/java-testing-junit-mockito && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "java-testing-junit-mockito" agent skill from https://github.com/makifbaysal/tasktrooper/tree/main/catalog/agents/backend-developer/skills/java-testing-junit-mockito into .cursor/skills/java-testing-junit-mockito/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "java-testing-junit-mockito", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/makifbaysal/tasktrooper.git --path catalog/agents/backend-developer/skills/java-testing-junit-mockito--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add makifbaysal/tasktrooper --skill java-testing-junit-mockito -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install makifbaysal/tasktrooper java-testing-junit-mockito --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/makifbaysal/tasktrooper.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/catalog/agents/backend-developer/skills/java-testing-junit-mockito .gemini/skills/java-testing-junit-mockito && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "java-testing-junit-mockito" agent skill from https://github.com/makifbaysal/tasktrooper/tree/main/catalog/agents/backend-developer/skills/java-testing-junit-mockito into .gemini/skills/java-testing-junit-mockito/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "java-testing-junit-mockito", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install makifbaysal/tasktrooper java-testing-junit-mockitoInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add makifbaysal/tasktrooper --skill java-testing-junit-mockito -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/makifbaysal/tasktrooper.git skills-src && mkdir -p .github/skills && cp -r skills-src/catalog/agents/backend-developer/skills/java-testing-junit-mockito .github/skills/java-testing-junit-mockito && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "java-testing-junit-mockito" agent skill from https://github.com/makifbaysal/tasktrooper/tree/main/catalog/agents/backend-developer/skills/java-testing-junit-mockito into .github/skills/java-testing-junit-mockito/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "java-testing-junit-mockito", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add makifbaysal/tasktrooper --skill java-testing-junit-mockito -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install makifbaysal/tasktrooper java-testing-junit-mockito --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/makifbaysal/tasktrooper.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/catalog/agents/backend-developer/skills/java-testing-junit-mockito .opencode/skills/java-testing-junit-mockito && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "java-testing-junit-mockito" agent skill from https://github.com/makifbaysal/tasktrooper/tree/main/catalog/agents/backend-developer/skills/java-testing-junit-mockito into .opencode/skills/java-testing-junit-mockito/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "java-testing-junit-mockito", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
java-testing-junit-mockitoA skill your agent uses when writing tests for Java (Quarkus or Spring) code - JUnit Jupiter structure, Mockito for collaborators, test slices, Testcontainers, and framework-native integration…
Java Testing Junit Mockito is an agent skill from makifbaysal/tasktrooper. Use when writing tests for Java (Quarkus or Spring) code - JUnit Jupiter structure, Mockito for collaborators, test slices, Testcontainers, and framework-native integration tests, test-first
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Integration testing, Unit testing and Test-driven development. It works with JUnit and Java. The repository describes itself as: Local-first agent platform: board + role agents + agent CLI runs (Claude Code, Cursor, Antigravity, OpenCode) or local and API models (Ollama, LM Studio), all on your own Mac. The licence is Apache-2.0.
Read from SKILL.md and the folder at commit f3d59b5. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are java).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Java Testing Junit Mockito loads about 1.1k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 435 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from makifbaysal/tasktrooper at commit f3d59b5, republished under its Apache-2.0 licence (© makifbaysal). 435 words, ~1,122 tokens.
.claude/skills/java-testing-junit-mockito/SKILL.md (or your agent's skills folder).Test-first in Java, same discipline as everywhere (see tdd-workflow): write the failing test, watch it fail, minimal code to pass. This skill is the Java mechanics for that cycle.
Core principle: Unit-test the domain and services as plain Java without booting the framework. Reserve framework-integration tests for the boundary (HTTP, persistence).
| Level | What it covers | Tools |
|---|---|---|
| Unit | Domain entity / value object, no mocks | JUnit Jupiter |
| Unit with mocks | Service (mock its ports) | JUnit Jupiter + Mockito |
| Persistence slice | Repository against a real DB, no HTTP layer | @DataJpaTest (Spring) + Testcontainers @ServiceConnection; Quarkus @QuarkusTest with Dev Services |
| Web slice | Controller/resource wiring, serialization, validation — mocked service | @WebMvcTest (Spring); Quarkus @QuarkusTest + @InjectMock |
| End-to-end | Full app boot, real DB, real HTTP | @SpringBootTest(webEnvironment=RANDOM_PORT) + RestTestClient (Spring Boot 4); @QuarkusTest + RestAssured |
Most tests are the first two — fast, no container. Boot the framework only where you're testing wiring, serialization, or SQL; reach for the narrowest slice that proves it before a full @SpringBootTest/plain @QuarkusTest.
class TaskServiceTest {
private final TaskRepository repo = mock(TaskRepository.class);
private final TaskService service = new TaskService(repo); // constructor injection pays off
@Test
void create_persists_and_returns_task() {
Task t = service.create("Write the report");
verify(repo).persist(any(Task.class)); // or save(...) for Spring
assertEquals("Write the report", t.title());
}
@Test
void create_rejects_blank_title() {
assertThrows(InvalidTaskTitle.class, () -> service.create(" "));
verifyNoInteractions(repo); // invalid input never hits the DB
}
}@Test, named for the behavior (create_rejects_blank_title).@ParameterizedTest for boundary tables (200 chars ok, 201 rejected).assertThat(...)) is fine and reads well; match the repo's existing assertion style.@MockitoBean/@MockitoSpyBean replace @MockBean/@SpyBean, which were removed in Boot 4.0 — use the old annotations only on a repo still pinned to Boot 3.x.@InjectMock inside a @QuarkusTest for a CDI-bean mock; RestAssured for the HTTP-level assertion: given().when().post("/tasks").then().statusCode(201).testcontainers-* (e.g. org.testcontainers:testcontainers-postgresql), class org.testcontainers.postgresql.PostgreSQLContainer; JUnit 4 support was removed, Jupiter only.mockito-core as a -javaagent in the build's surefire/failsafe config if the repo doesn't already, to avoid the dynamic-agent-loading warning.@SpringBootTest/plain @QuarkusTest on everything — slow, and hides design problems that plain unit tests would surface.verify(mock) only, never checking the returned/observable value.@MockBean on a Spring Boot 4 repo (removed; use @MockitoBean).© makifbaysal, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in catalog/agents/backend-developer/skills/java-testing-junit-mockito of makifbaysal/tasktrooper.
Open the folder on GitHubat commit f3d59b5
Java Testing Junit Mockito next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Java Testing Junit Mockito this skillmakifbaysal/tasktrooper | 109 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Junit 5 Skillsickn33/agentic-awesome-skills | 47k | 1 repos | ~1.8k | Automated safety check: Pass | MIT | |
| TDD GuideLeoYeAI/openclaw-master-skills | 2.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Test Driven GenerationArabelaTso/Skills-4-SE | 253 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Rust Testingkurealnum/dotfiles | 290 | 6 repos | ~2.9k | Automated safety check: Pass | None | |
| Springboot TDDaffaan-m/ECC | 274k | 5 repos | ~947 | Automated safety check: Pass | MIT |
sickn33/agentic-awesome-skills
Generates production-grade JUnit 5 unit and integration tests in Java.
LeoYeAI/openclaw-master-skills
Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and…
ArabelaTso/Skills-4-SE
Generate implementation code that passes existing unit tests.
kurealnum/dotfiles
Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage.
affaan-m/ECC
Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo.
eclipse-rdf4j/rdf4j
Debug Maven Surefire unit tests by running them in JDWP "wait for debugger" mode (-Dmaven.surefire.debug) and attaching to the forked test JVM using jdb (preferred for CLI/agent debugging)…
makifbaysal/tasktrooper
A skill your agent uses when a task adds or changes an HTTP endpoint, its request/response shape, status codes, auth or error format - the request matrix, curl templates and what counts as a…
makifbaysal/tasktrooper
A skill your agent uses when writing acceptance criteria for a task - express each as an observable Given/When/Then that QA can execute, including negative cases
makifbaysal/tasktrooper
A skill your agent uses when a task changes any screen, form, dialog, menu or control - Lighthouse/axe scan of the changed screens, a keyboard walk, and the thresholds that fail a task
makifbaysal/tasktrooper
A skill your agent uses when deciding whether a request needs an analiz task before implementation - the conditions that require the architect's analysis versus going straight to implementation
makifbaysal/tasktrooper
A skill your agent uses when you write or revise the analiz deliverable - the ONE self-contained HTML report (spec and plan as sections) a human reviews passage by passage
makifbaysal/tasktrooper
A skill your agent uses when you finish an analiz report - the human must approve the analysis before any implementation task is created, via the analizreview column
Categories
A skill your agent uses when writing tests for Java (Quarkus or Spring) code - JUnit Jupiter structure, Mockito for collaborators, test slices, Testcontainers, and framework-native integration…. Java Testing Junit Mockito is an agent skill from makifbaysal/tasktrooper.
Java Testing Junit Mockito fits situations like: writing tests for Java (Quarkus; spring) code - JUnit Jupiter structure; mockito for collaborators; framework-native integration tests.
Run `npx skills add makifbaysal/tasktrooper --skill java-testing-junit-mockito -a claude-code`. Or copy the skill folder (catalog/agents/backend-developer/skills/java-testing-junit-mockito in makifbaysal/tasktrooper) into .claude/skills/java-testing-junit-mockito in your project. Claude Code loads it when a task matches its description.
Run `npx skills add makifbaysal/tasktrooper --skill java-testing-junit-mockito -a codex`. Or copy the skill folder (catalog/agents/backend-developer/skills/java-testing-junit-mockito in makifbaysal/tasktrooper) into .agents/skills/java-testing-junit-mockito in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add makifbaysal/tasktrooper --skill java-testing-junit-mockito -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/java-testing-junit-mockito, .gemini/skills/java-testing-junit-mockito, .github/skills/java-testing-junit-mockito and .opencode/skills/java-testing-junit-mockito in your project.
SKILL.md names no scripts, command-line tools or credentials: Java Testing Junit Mockito is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Java Testing Junit Mockito is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Java Testing Junit Mockito: Junit 5 Skill (sickn33/agentic-awesome-skills, 47k stars), TDD Guide (LeoYeAI/openclaw-master-skills, 2.2k stars), Test Driven Generation (ArabelaTso/Skills-4-SE, 253 stars) and Rust Testing (kurealnum/dotfiles, 290 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
makifbaysal (a GitHub user) maintains it in makifbaysal/tasktrooper, which has 109 GitHub stars. The repository holds 99 skills in this directory. The repository was last updated on October 6, 2026.
Source: makifbaysal/tasktrooper on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.