agentleFS
Sign inStart free
jabrenajabrena/cursor-rules-java/skills/132-java-testing-integration-testing/SKILL.md

132-java-testing-integration-testing

Skill452 starsChanged 3 months agoApache-2.0View on GitHub

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

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before applying any integration test changes, ensure the project compiles.

    line 31
  2. Very specific:

    MANDATORY: Run ./mvnw compile or mvn compile before applying any change

    line 33
  3. Distinctive:

    SAFETY: If compilation fails, stop immediately and do not proceed — compilation failure is a blocking condition

    line 34
  4. Very specific:

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

    line 35
  5. Distinctive:

    BEFORE APPLYING: Read the reference for detailed examples, good/bad patterns, and constraints

    line 36
  6. Distinctive:

    Write Java integration tests with real infrastructure boundaries

    line 42
  7. Very specific:

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

    line 50
  8. Very specific:

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

    line 54
  9. Very specific:

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

    line 62

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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
  • 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

  1. Compile project before integration-test changes

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

  1. Read integration-testing reference and detect topology

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

  1. Set up resilient integration-test infrastructure

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

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free