How do I install the 132 Java Testing Integration Testing skill?

Run npx skillmds add majiayu000/132-java-testing-integration-testing-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is 132 Java Testing Integration Testing safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with 132 Java Testing Integration Testing?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is 132 Java Testing Integration Testing free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published 132 Java Testing Integration Testing?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

132 Java Testing Integration Testing by majiayu000

Name: 132 Java Testing Integration Testing
Rating: 4.2 (5 reviews)
Author: majiayu000

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. This should trigger for requests such as Review Java code for integration tests; Apply best practices for integration tests in Java code. Part of cursor-rules-java project

majiayu000 c7c5c0f 2 files · 4.3 KB Updated Sep 9, 2026 567 repo stars

File contents

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

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.

---name: 132-java-testing-integration-testing-2description: 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. Part of cursor-rules-java projectlicense: Apache-2.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 ## Workflow 1. **Compile project before integration-test changes** Run `./mvnw compile` or `mvn compile` and stop immediately if compilation fails. 2. **Read integration-testing reference and detect topology** Read `references/132-java-testing-integration-testing.md` and detect HTTP client and external dependency integration points. 3. **Set up resilient integration-test infrastructure** Implement BaseIntegrationTest, WireMock mappings/stubs, per-test isolation, and verification patterns. 4. **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](references/132-java-testing-integration-testing.md).

Frequently asked questions