Cursor-rules-java 132-java-testing-integration-testing

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. Part of the skills-for-java project

install

source · Clone the upstream repo

git clone https://github.com/jabrena/cursor-rules-java

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/jabrena/cursor-rules-java "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/132-java-testing-integration-testing" ~/.claude/skills/jabrena-cursor-rules-java-132-java-testing-integration-testing && rm -rf "$T"

manifest: skills/132-java-testing-integration-testing/SKILL.md

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

Reference

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