Agent skill

132 Java Testing Integration Testing

A skill your agent uses when you need to set up, review, or improve Java integration tests — including generating a BaseIntegrationTest.java with WireMock for HTTP stubs, detecting HTTP client…

Apache-2.0Auto-check passedTesting & QA

Install 132 Java Testing Integration Testing

skills CLI

$ npx skills add jabrena/plinth --skill 132-java-testing-integration-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install jabrena/plinth 132-java-testing-integration-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/132-java-testing-integration-testing .claude/skills/132-java-testing-integration-testing && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "132-java-testing-integration-testing" agent skill from https://github.com/jabrena/plinth/tree/main/skills/132-java-testing-integration-testing into .claude/skills/132-java-testing-integration-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "132-java-testing-integration-testing", 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

$skill-installer install https://github.com/jabrena/plinth/tree/main/skills/132-java-testing-integration-testing

Type 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.

skills CLI

$ npx skills add jabrena/plinth --skill 132-java-testing-integration-testing -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install jabrena/plinth 132-java-testing-integration-testing --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/132-java-testing-integration-testing .agents/skills/132-java-testing-integration-testing && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "132-java-testing-integration-testing" agent skill from https://github.com/jabrena/plinth/tree/main/skills/132-java-testing-integration-testing into .agents/skills/132-java-testing-integration-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "132-java-testing-integration-testing", 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.

skills CLI

$ npx skills add jabrena/plinth --skill 132-java-testing-integration-testing -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install jabrena/plinth 132-java-testing-integration-testing --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/132-java-testing-integration-testing .cursor/skills/132-java-testing-integration-testing && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "132-java-testing-integration-testing" agent skill from https://github.com/jabrena/plinth/tree/main/skills/132-java-testing-integration-testing into .cursor/skills/132-java-testing-integration-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "132-java-testing-integration-testing", 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

$ gemini skills install https://github.com/jabrena/plinth.git --path skills/132-java-testing-integration-testing

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add jabrena/plinth --skill 132-java-testing-integration-testing -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install jabrena/plinth 132-java-testing-integration-testing --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/132-java-testing-integration-testing .gemini/skills/132-java-testing-integration-testing && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "132-java-testing-integration-testing" agent skill from https://github.com/jabrena/plinth/tree/main/skills/132-java-testing-integration-testing into .gemini/skills/132-java-testing-integration-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "132-java-testing-integration-testing", 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.

GitHub CLI

$ gh skill install jabrena/plinth 132-java-testing-integration-testing

Installs 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).

skills CLI

$ npx skills add jabrena/plinth --skill 132-java-testing-integration-testing -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/132-java-testing-integration-testing .github/skills/132-java-testing-integration-testing && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "132-java-testing-integration-testing" agent skill from https://github.com/jabrena/plinth/tree/main/skills/132-java-testing-integration-testing into .github/skills/132-java-testing-integration-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "132-java-testing-integration-testing", 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.

skills CLI

$ npx skills add jabrena/plinth --skill 132-java-testing-integration-testing -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install jabrena/plinth 132-java-testing-integration-testing --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/132-java-testing-integration-testing .opencode/skills/132-java-testing-integration-testing && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "132-java-testing-integration-testing" agent skill from https://github.com/jabrena/plinth/tree/main/skills/132-java-testing-integration-testing into .opencode/skills/132-java-testing-integration-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "132-java-testing-integration-testing", 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.

Facts

Skill name: 132-java-testing-integration-testing
GitHub stars: 446
Token cost: ~965 tokens
SKILL.md length: 322 words
Files: 2 (incl. references)
Skills in repo: 124
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

A skill your agent uses when you need to set up, review, or improve Java integration tests — including generating a BaseIntegrationTest.java with WireMock for HTTP stubs, detecting HTTP client…

You need to set up
SKILL.md covers Constraints, When to use this skill, Workflow and Reference
Calls mvn
Improve Java integration tests — including generating a BaseIntegrationTest.java with WireMock for HTTP stubs

What it does

132 Java Testing Integration Testing is an agent skill from jabrena/plinth. Use when you need to set up, review, or improve Java integration tests — including generating a BaseIntegrationTest.java with WireMock for HTTP stubs, detecting HTTP client infrastructure from import signals, injecting service coordinates dynamically via System.setProperty(), creating WireMock JSON mapping files with bodyFileName, isolating stubs per test method, verifying HTTP interactions, or eliminating anti-patterns such as Mockito-mocked HTTP clients or globally registered WireMock stubs. This should trigger…

Its SKILL.md is about 970 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/132-java-testing-integration-testing.md`).

It sits in Testing & QA, covering Integration testing. It works with Java. The repository describes itself as: Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers. The licence is Apache-2.0.

When your agent uses it

You need to set up
Improve Java integration tests — including generating a BaseIntegrationTest.java with WireMock for HTTP stubs
Detecting HTTP client infrastructure from import signals
Injecting service coordinates dynamically via System.setProperty()

Example prompts

“/132-java-testing-integration-testing”

What it can do on your machine

Read from SKILL.md and the folder at commit dca88dc. It shows what the files ask for, not the result of running them.

Tool permissions
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.
Runs code
Shell commands in SKILL.md call:
- mvn
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

132 Java Testing Integration Testing loads about 965 tokens when it runs, and up to ~6.9k if it reads all its reference files. Until then it costs about 220 tokens; SKILL.md has 322 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~220
When it runs · the whole SKILL.md, loaded when a task matches: ~965
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~6.9k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from jabrena/plinth at commit dca88dc, republished under its Apache-2.0 licence (© jabrena). 322 words, ~965 tokens.

Download SKILL.mdSave it as .claude/skills/132-java-testing-integration-testing/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: 132-java-testing-integration-testing
description: Use when you need to set up, review, or improve Java integration tests — including generating a BaseIntegrationTest.java with WireMock for HTTP stubs, detecting HTTP client infrastructure from import signals, injecting service coordinates dynamically via System.setProperty(), creating WireMock JSON mapping files with bodyFileName, isolating stubs per test method, verifying HTTP interactions, or eliminating anti-patterns such as Mockito-mocked HTTP clients or globally registered WireMock stubs. This should trigger for requests such as Review Java code for integration tests; Apply best practices for integration tests in Java code; Write Java integration tests with real infrastructure boundaries; Improve Testcontainers integration tests for Java code; Review integration test setup and teardown in Java projects. Part of Plinth Toolkit
license: Apache-2.0
metadata.author: Juan Antonio Breña Moral
metadata.version: 0.19.0

Java Integration testing guidelines

Set up robust integration-test infrastructure for Java services using WireMock to stub outbound HTTP dependencies.

What is covered in this Skill?

Infrastructure topology detection: scanning imports for HttpClient, feign.*, retrofit2.*, RestTemplate
Abstract BaseIntegrationTest base class
WireMockExtension with @RegisterExtension, dynamic port allocation (dynamicPort())
usingFilesUnderClasspath(wiremock), @BeforeAll + System.setProperty() for coordinate propagation
WireMock JSON mapping files (bodyFileName referencing wiremock/files/)
Programmatic stub registration via WireMock DSL
Per-test stub isolation: register stubs inside each test method
Fault injection: 503 service unavailable, network latency with withFixedDelay
Request verification via WIREMOCK.verify
wiremock-standalone Maven dependency (test scope)
Anti-patterns: global @BeforeAll stubs, Mockito-mocked HTTP clients, hardcoded ports or URLs

Scope: The reference is organized by examples (good/bad code patterns) for each core area. Apply recommendations based on applicable examples.

Constraints

Before applying any integration test changes, ensure the project compiles. If compilation fails, stop immediately — do not proceed until resolved. After applying improvements, run full verification.

MANDATORY: Run ./mvnw compile or mvn compile before applying any change
SAFETY: If compilation fails, stop immediately and do not proceed — compilation failure is a blocking condition
VERIFY: Run ./mvnw clean verify or mvn clean verify after applying improvements
BEFORE APPLYING: Read the reference for detailed examples, good/bad patterns, and constraints

When to use this skill

Review Java code for integration tests
Apply best practices for integration tests in Java code
Write Java integration tests with real infrastructure boundaries
Improve Testcontainers integration tests for Java code
Review integration test setup and teardown in Java projects

Workflow

Compile project before integration-test changes

Run ./mvnw compile or mvn compile and stop immediately if compilation fails.

Read integration-testing reference and detect topology

Read references/132-java-testing-integration-testing.md and detect HTTP client and external dependency integration points.

Set up resilient integration-test infrastructure

Implement BaseIntegrationTest, WireMock mappings/stubs, per-test isolation, and verification patterns.

Verify with full build

Run ./mvnw clean verify or mvn clean verify after applying improvements.

Reference

For detailed guidance, examples, and constraints, see references/132-java-testing-integration-testing.md.

Files

SKILL.md and 1 other file (references) in skills/132-java-testing-integration-testing of jabrena/plinth.

SKILL.md
references/132-java-testing-integration-testing.md

Open the folder on GitHubat commit dca88dc

Compare with similar skills

132 Java Testing Integration Testing 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.

132 Java Testing Integration Testing compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
132 Java Testing Integration Testing this skilljabrena/plinth	446	—	~965	Automated safety check: Pass	Apache-2.0	yesterday
Java SDK E2E Test with Replay Snapshotgithub/copilot-sdk	11k	—	~1.8k	Automated safety check: Pass	MIT	today
Update All Versionsgroovy/GMavenPlus	306	—	~807	Automated safety check: Pass	Custom licence	3 mo ago
Add Gc TestDataDog/jmxfetch	109	—	~1.1k	Automated safety check: Pass	Custom licence	2 mo ago
Reprovaadin/flow-components	129	—	~1.3k	Automated safety check: Pass	None	yesterday
Testcontainers Guide Migratordocker/docs	4.7k	—	~5k	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

Java SDK E2E Test with Replay Snapshot
github/copilot-sdk
Official
Creates a Java SDK end-to-end test for the Copilot SDK that runs against a recorded YAML snapshot through a replay proxy, so CI needs no real authentication.
11k GitHub stars~1.8k tokensUpdated today
Testing & QAAuto-check passed
Update All Versions
groovy/GMavenPlus
A skill your agent uses when refreshing GMavenPlus Groovy support, Maven dependency and plugin versions, and integration-test POM versions.
306 GitHub stars~807 tokensUpdated 3 mo ago
Testing & QAAuto-check passed
Add Gc Test
DataDog/jmxfetch
Official
Add integration tests to TestGCMetrics.java for new GC collector support added to new-gc-default-jmx-metrics.yaml.
109 GitHub stars~1.1k tokensUpdated 2 mo ago
Testing & QAAuto-check passed
Repro
vaadin/flow-components
Reproduce a Vaadin Flow component bug from a GitHub issue in vaadin/flow-components or a component-specific issue in vaadin/flow.
129 GitHub stars~1.3k tokensUpdated yesterday
Testing & QAAuto-check passed
Testcontainers Guide Migrator
docker/docs
Official
Migrate a Testcontainers guide from testcontainers.com into the Docker docs site (docs.docker.com).
4.7k GitHub stars~5k tokensUpdated yesterday
Testing & QAAuto-check passed
Validation
josstei/maestro-orchestrate
Cross-cutting validation methodology for verifying phase outputs and project integrity
465 GitHub stars~2.3k tokensUpdated yesterday
Testing & QAAuto-check passed

More from jabrena/plinth

All 124 skills in this repo

703 Technologies Fuzzing Testing
jabrena/plinth
A skill your agent uses when you need to add or review fuzz testing for Java APIs with CATS — including contract-driven negative testing, malformed payload validation, boundary input exploration, CI…
446 GitHub stars~874 tokensUpdated yesterday
Auto-check passed
033 Architecture Diagrams
jabrena/plinth
A skill your agent uses when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams…
446 GitHub stars~3.1k tokensUpdated yesterday
Auto-check passed
112 Java Maven Plugins
jabrena/plinth
A skill your agent uses when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning…
446 GitHub stars~3.2k tokensUpdated yesterday
Auto-check passed
151 Java Performance Jmeter
jabrena/plinth
A skill your agent uses when you need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template, configuring load tests with…
446 GitHub stars~842 tokensUpdated yesterday
Auto-check passed
161 Java Profiling Detect
jabrena/plinth
A skill your agent uses when you need to set up Java application profiling to detect and measure performance issues — including trusted preinstalled async-profiler v4.x setup, problem-driven…
446 GitHub stars~903 tokensUpdated yesterday
Auto-check passed
001 Commands Inventory
jabrena/plinth
A skill your agent uses when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the…
446 GitHub stars~697 tokensUpdated yesterday
Auto-check passed

Works with

Java

Questions about 132 Java Testing Integration Testing

What does 132 Java Testing Integration Testing do?

A skill your agent uses when you need to set up, review, or improve Java integration tests — including generating a BaseIntegrationTest.java with WireMock for HTTP stubs, detecting HTTP client…. 132 Java Testing Integration Testing is an agent skill from jabrena/plinth.setProperty(), creating WireMock JSON mapping files with bodyFileName, isolating stubs per test method, verifying HTTP interactions, or eliminating anti-patterns such as Mockito-mocked HTTP clients or globally registered WireMock stubs.

When should I use 132 Java Testing Integration Testing?

132 Java Testing Integration Testing fits situations like: you need to set up; improve Java integration tests — including generating a BaseIntegrationTest.java with WireMock for HTTP stubs; detecting HTTP client infrastructure from import signals; injecting service coordinates dynamically via System.setProperty().

How do I install 132 Java Testing Integration Testing in Claude Code?

Run `npx skills add jabrena/plinth --skill 132-java-testing-integration-testing -a claude-code`. Or copy the skill folder (skills/132-java-testing-integration-testing in jabrena/plinth) into .claude/skills/132-java-testing-integration-testing in your project. Claude Code loads it when a task matches its description.

How do I install 132 Java Testing Integration Testing in Codex?

Run `npx skills add jabrena/plinth --skill 132-java-testing-integration-testing -a codex`. Or copy the skill folder (skills/132-java-testing-integration-testing in jabrena/plinth) into .agents/skills/132-java-testing-integration-testing in your project. Codex loads it when a task matches its description.

Can I use 132 Java Testing Integration Testing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jabrena/plinth --skill 132-java-testing-integration-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/132-java-testing-integration-testing, .gemini/skills/132-java-testing-integration-testing, .github/skills/132-java-testing-integration-testing and .opencode/skills/132-java-testing-integration-testing in your project.

What does 132 Java Testing Integration Testing need to run?

Going by SKILL.md and its folder, 132 Java Testing Integration Testing needs the command-line tools its instructions call (mvn).

Does 132 Java Testing Integration Testing access the network?

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.

Is 132 Java Testing Integration Testing safe to install?

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.

What licence does 132 Java Testing Integration Testing use?

132 Java Testing Integration Testing is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does 132 Java Testing Integration Testing use?

About 965 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.9k tokens, read only when the agent opens those files.

What are the alternatives to 132 Java Testing Integration Testing?

Skills that share tags, products or a category with 132 Java Testing Integration Testing: Java SDK E2E Test with Replay Snapshot (github/copilot-sdk, 11k stars), Update All Versions (groovy/GMavenPlus, 306 stars), Add Gc Test (DataDog/jmxfetch, 109 stars) and Repro (vaadin/flow-components, 129 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains 132 Java Testing Integration Testing?

jabrena (a GitHub user) maintains it in jabrena/plinth, which has 446 GitHub stars. The repository holds 124 skills in this directory. The repository was last updated on October 7, 2026.

Source: jabrena/plinth on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install 132 Java Testing Integration Testing

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Java Integration testing guidelines

Constraints

When to use this skill

Workflow

Reference

Files

Compare with similar skills

Similar skills

More from jabrena/plinth

Related

Questions about 132 Java Testing Integration Testing