132 Java Testing Integration Testing

This is a solid foundation for Java integration testing that pushes you toward WireMock over Mockito for HTTP mocking. It scans your imports to detect HTTP clients (Feign, Retrofit, RestTemplate), then sets up a BaseIntegrationTest with dynamic port allocation and proper stub isolation per test method. The workflow is strict about compilation checks before making changes, which will save you from breaking things. What I like here is the explicit anti-pattern list: no global stubs, no hardcoded ports, no mocking HTTP clients with Mockito. It's opinionated in a good way. Use this when you're setting up or cleaning up integration test infrastructure and want WireMock best practices baked in from the start.

skills.sh installs: 128
GitHub stars: 393
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add jabrena/cursor-rules-java --skill 132-java-testing-integration-testing --agent claude-code

Installs into .claude/skills of the current project.

Files

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