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; 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

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/132-java-testing-integration-testing/SKILL.md

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized overview with excellent progressive disclosure and clear validation-gated workflow. Its main weakness is actionability: the body itself contains no executable code, relying entirely on the reference for the actual examples.

Suggestions

Inline one minimal executable snippet (e.g. a BaseIntegrationTest + WireMockExtension skeleton or a System.setProperty coordinate-injection line) so the body is self-sufficient for the most common case.

Fold the 'When to use this skill' section away or trim it, since its trigger phrases duplicate the frontmatter description.

Surface the compile-failure recovery loop explicitly in the workflow (fix → re-compile → proceed) rather than only in the reference.

Dimension	Reasoning	Score
Conciseness	The body is lean — a coverage bullet list, constraints, a 4-step workflow, and a single reference link — with only minor redundancy where 'When to use this skill' repeats triggers already in the description.	4 / 5
Actionability	Concrete commands ('./mvnw compile', './mvnw clean verify') and specific class names are present, but no executable code appears inline — all code examples are delegated to the reference, leaving gaps for a self-contained body.	3 / 5
Workflow Clarity	A clear 4-step sequence with explicit validation checkpoints (compile-before, stop-on-failure, verify-after); the fix-and-retry recovery loop is described only in the reference rather than the body, so it falls just short of the top anchor.	4 / 5
Progressive Disclosure	A concise overview pointing to a single, clearly signaled one-level-deep reference (references/132-java-testing-integration-testing.md, verified present and well-structured at 494 lines), with content appropriately split between SKILL.md and the reference.	5 / 5
	Total	16 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with explicit trigger guidance and concrete capability enumeration. It would reach the top level by adopting third-person voice and adding the Spring Boot/Quarkus disambiguation pointers that the reference already contains.

Suggestions

Rewrite in third person ('Use when setting up, reviewing, or improving Java integration tests…') to remove the second-person 'you need to' and recover the specificity point.

Add the sibling-skill disambiguation from the reference ('For Spring Boot use @322…; For Quarkus use @422…') to reduce conflict risk with framework-specific testing skills.

Reconcile the Testcontainers trigger with the skill's WireMock-focused scope, or drop it if Testcontainers is not a primary capability.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions ('generating a BaseIntegrationTest.java with WireMock', 'injecting service coordinates dynamically via System.setProperty()', 'creating WireMock JSON mapping files with bodyFileName') — anchor 5 coverage, reduced by 1 for second-person voice ('Use when you need to').	4 / 5
Completeness	Explicitly answers both 'what' (the long list of setup/review/anti-pattern actions) and 'when' ('This should trigger for requests such as…') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases users would say ('Review Java code for integration tests', 'Write Java integration tests with real infrastructure boundaries', 'Improve Testcontainers integration tests for Java code') give good coverage, though a few common phrasings are missing.	4 / 5
Distinctiveness Conflict Risk	Clear Java-integration-test-with-WireMock niche with distinct triggers, but the Testcontainers mention and absence of sibling-skill disambiguation (which the reference file includes) leave minor overlap risk.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/plinth
Path: skills/132-java-testing-integration-testing/SKILL.md
Commit: 77b8825

Reviewed: about 23 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.