132-java-testing-integration-testing

A guide for setting up Java integration tests, which test several application parts together and use WireMock to imitate external HTTP services.

In plain words
What is it for?
Use it to create or improve Java integration tests, including WireMock setup, HTTP fault simulation, per-test stubs, and request verification.
Why use it?
It removes guesswork around test infrastructure, service configuration, request stubs, failure scenarios, and checking outgoing requests.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/jabrena/cursor-rules-examples/132-java-testing-integration-testing
Any agent
npx skills add jabrena/cursor-rules-examples --skill 132-java-testing-integration-testing
Clone the repo
git clone --depth 1 https://github.com/jabrena/cursor-rules-examples

Made for: Claude Code, Codex.

Per session 105 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 592 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00105 $0.00592
Opus 5 $0.00053 $0.00296
Sonnet 5 $0.00021 $0.00118
Haiku 4.5 $0.00011 $0.00059

Measured yesterday against content hash 6085d5c88b72, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

132-java-testing-integration-testing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/132-java-testing-integration-testing/SKILL.md · 46 lines

How it starts

The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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.

Read the full file on GitHub · 46 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 46 lines · 105 tokens per session scan A 6085d5c88b72

Subscribe to this mod's changes

132-java-testing-integration-testing is a skill published in the GitHub repository jabrena/cursor-rules-examples (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 105 tokens to every session and 592 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

complexity

Wire and satisfy cyclomatic complexity lint. Detect the repo's existing linter, set or keep a cap (default 10), extract until green, never disable the rule. Use when complexity.mdc globs match, lint reports C901/complexity, or the user asks for simpler / less nested code.

kleosr/kleosrules · 66 tokens

uikit-expert

Write, review, or improve UIKit code following best practices for view controller lifecycle, Auto Layout, collection views, navigation, animation, memory management, and modern iOS 18–26 APIs. Use when building new UIKit features, refactoring existing views or view controllers, reviewing code quality, adopting modern…

zinxj/uikit-expert-skill · 95 tokens

debugging

Debugs difficult, intermittent, cross-layer, or regression bugs evidence before fixes. Use when the cause is unknown, normal debugging stalled, or the user asks to hunt, diagnose, or root-cause a bug.

kleosr/kleosrules · 46 tokens

redesign-existing-projects

Elaya audit for existing sites/apps that look generic, cheap, or AI-made. Diagnose first, then fix in place (fonts, color, states, layout, motion). Use when Mario says polish, audit, upgrade, or it looks horrible. Product apps apply diagnosis through premium-ui-craft values, not Elaya black/Geist/700ms. Upstream…

kleosr/kleosrules · 92 tokens

testing

Test writing workflows: TDD order, mocks, house gauntlet, regression naming. Use when writing/editing tests or when testing.mdc globs match. Thin rule = roofs; this skill = procedure.

kleosr/kleosrules · 45 tokens

design-stack

Router for Mario's Design agent. Picks one UI skill plus premium-ui-craft. Use at the start of any Product Designer / @Design / UX/UI turn.

kleosr/kleosrules · 36 tokens