DevOps & Infra
322-frameworks-spring-boot-testing-integration-tests - Claude MCP Skill
Use when you need to write or improve integration tests — including Testcontainers with @ServiceConnection, @DataJdbcTest persistence slices, TestRestTemplate or MockMvcTester for HTTP, data isolation, and container lifecycle management for Spring Boot 4.0.x. This should trigger for requests such as Review Java code for Spring Boot integration tests; Apply best practices for Spring Boot integration tests in Java code; Write @SpringBootTest integration tests with Testcontainers; Configure dynamic properties for Spring integration tests; Review Spring Boot integration test profiles. Part of Plinth Toolkit
SEO Guide: Enhance your AI agent with the 322-frameworks-spring-boot-testing-integration-tests tool. This Model Context Protocol (MCP) server allows Claude Desktop and other LLMs to use when you need to write or improve integration tests — including testcontainers with @serviceconn... Download and configure this skill to unlock new capabilities for your AI workflow.
Documentation
SKILL.md# Spring Boot Integration Testing Apply Spring Boot integration testing guidelines for Spring Boot 4.0.x. **What is covered in this Skill?** - Integration test scope and purpose (verify wiring and contracts, not unit-test duplication) - Testcontainers with @ServiceConnection for zero-config wiring (preferred) - @DynamicPropertySource as fallback for containers without built-in service connection support - Static @Container instances shared across test methods for performance - MockMvcTester for fluent AssertJ-based HTTP assertions (Spring Boot 4.0.x) - TestRestTemplate for full HTTP stack testing - @DataJdbcTest / @DataJpaTest persistence slices (load only persistence layer, start faster) - Data isolation: each test owns its scenario; no shared mutable state or ordering assumptions - @MockitoBean for mock registration (Spring Boot 4.0.x — @MockBean removed) - Resource lifecycle: Testcontainers JUnit integration for teardown; *IT / integration test separation **Scope:** Apply recommendations based on the reference rules and good/bad code examples. ## Constraints Before applying any integration test changes, ensure the project compiles. If compilation fails, stop immediately. After applying improvements, run full verification. - **MANDATORY**: Run `./mvnw compile` or `mvn compile` before applying any change - **SAFETY**: If compilation fails, stop immediately - **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` after applying improvements - **BEFORE APPLYING**: Read the reference for detailed rules and good/bad patterns - **EDGE CASE**: If request scope is ambiguous, stop and ask a clarifying question before applying changes - **EDGE CASE**: If required inputs, files, or tooling are missing, report what is missing and ask whether to proceed with setup guidance ## When to use this skill - Review Java code for Spring Boot integration tests - Apply best practices for Spring Boot integration tests in Java code - Write @SpringBootTest integration tests with Testcontainers - Configure dynamic properties for Spring integration tests - Review Spring Boot integration test profiles ## Workflow 1. **Read reference and assess project context** Read `references/322-frameworks-spring-boot-testing-integration-tests.md` and inspect the current project setup before proposing changes. 2. **Gather scope and decide target improvements** Identify requested outcomes, constraints, and the minimum safe set of changes to apply. 3. **Apply framework-aligned changes** Implement or refactor configuration/code following the reference patterns and project conventions. 4. **Run verification and report results** Execute appropriate build/tests and summarize what changed, what was verified, and any follow-up actions. ## Reference For detailed guidance, examples, and constraints, see [references/322-frameworks-spring-boot-testing-integration-tests.md](references/322-frameworks-spring-boot-testing-integration-tests.md).
Signals
Information
- Repository
- jabrena/cursor-rules-java
- Author
- jabrena
- Last Sync
- 9/5/2026
- Repo Updated
- 9/4/2026
- Created
- 3/19/2026
Reviews (0)
No reviews yet. Be the first to review this skill!
Related Skills
upgrade-nodejs
Upgrading Bun's Self-Reported Node.js Version
cursorrules
CrewAI Development Rules
firecrawl-build-search
Integrate Firecrawl `/search` into product code and agent workflows. Use when an app needs discovery before extraction, when the feature starts with a query instead of a URL, or when the system should search the web and optionally hydrate result content.
firecrawl-build-onboarding
Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.
Related Guides
Mastering the Oracle CLI: A Complete Guide to the Claude Skill for Database Professionals
Learn how to use the oracle Claude skill. Complete guide with installation instructions and examples.
Python Django Best Practices: A Comprehensive Guide to the Claude Skill
Learn how to use the python django best practices Claude skill. Complete guide with installation instructions and examples.
Mastering Python Development with Claude: A Complete Guide to the Python Skill
Learn how to use the python Claude skill. Complete guide with installation instructions and examples.