spring-boot-integration
Spring Boot integration testing with Testcontainers, sliced tests, and full context. Covers real database testing, API integration, and end-to-end flows. USE WHEN: user mentions "spring integration test", "testcontainers spring", "full context test", asks about "@SpringBootTest webEnvironment", "integration test database", "API integration test" DO NOT USE FOR: Unit tests - use `junit`; Slice tests only - use `spring-boot-test`; REST client testing - use `rest-assured`; E2E browser tests - use Selenium
What this skill does
# Spring Boot Integration Testing
> **Deep Knowledge**: Use `mcp__documentation__fetch_docs` with technology: `spring-boot-test` for comprehensive documentation.
## When NOT to Use This Skill
- **Pure Unit Tests** - Use `junit` with Mockito for isolated tests
- **Slice Tests Only** - Use `spring-boot-test` for @WebMvcTest, @DataJpaTest
- **REST Client Testing** - Use `rest-assured` for HTTP/API testing
- **E2E Browser Tests** - Use Selenium or Playwright
- **Contract Testing** - Use Spring Cloud Contract
## Test Annotations
### Full Context
```java
@SpringBootTest(webEnvironment = WebEnvironment.RANDOM_PORT)
class FullIntegrationTest {
@LocalServerPort
private int port;
@Autowired
private TestRestTemplate restTemplate;
}
```
### Sliced Tests
```java
// Controller layer only
@WebMvcTest(UserController.class)
class UserControllerTest {
@Autowired MockMvc mockMvc;
@MockBean UserService userService;
}
// Repository layer only
@DataJpaTest
class UserRepositoryTest {
@Autowired TestEntityManager entityManager;
@Autowired UserRepository repository;
}
// MongoDB layer only
@DataMongoTest
class ProductRepositoryTest {
@Autowired MongoTemplate mongoTemplate;
}
// JSON serialization
@JsonTest
class UserJsonTest {
@Autowired JacksonTester<User> json;
}
```
## MockMvc Patterns
### GET Request
```java
mockMvc.perform(get("/api/users/{id}", 1)
.accept(MediaType.APPLICATION_JSON))
.andExpect(status().isOk())
.andExpect(jsonPath("$.name").value("John"))
.andExpect(jsonPath("$.email").value("[email protected]"));
```
### POST Request
```java
mockMvc.perform(post("/api/users")
.contentType(MediaType.APPLICATION_JSON)
.content("""
{"name": "John", "email": "[email protected]"}
"""))
.andExpect(status().isCreated())
.andExpect(header().exists("Location"))
.andExpect(jsonPath("$.id").isNumber());
```
### With Authentication
```java
@WithMockUser(roles = "ADMIN")
@Test
void adminCanDeleteUser() throws Exception {
mockMvc.perform(delete("/api/users/1"))
.andExpect(status().isNoContent());
}
// Or with custom user
mockMvc.perform(get("/api/profile")
.with(user("john").roles("USER")))
.andExpect(status().isOk());
```
### Error Handling
```java
@Test
void shouldReturn404WhenNotFound() throws Exception {
when(userService.findById(99L))
.thenThrow(new ResourceNotFoundException("User not found"));
mockMvc.perform(get("/api/users/99"))
.andExpect(status().isNotFound())
.andExpect(jsonPath("$.message").value("User not found"));
}
```
## @DataJpaTest Patterns
### With Real Database
```java
@DataJpaTest
@AutoConfigureTestDatabase(replace = Replace.NONE) // Don't replace with H2
@Testcontainers
class UserRepositoryTest {
@Container
@ServiceConnection
static PostgreSQLContainer<?> postgres =
new PostgreSQLContainer<>("postgres:16-alpine");
@Autowired
private UserRepository repository;
@Test
void shouldFindByEmail() {
repository.save(new User("John", "[email protected]"));
Optional<User> found = repository.findByEmail("[email protected]");
assertThat(found).isPresent();
}
@Test
void shouldFindActiveUsers() {
repository.save(User.builder().name("Active").active(true).build());
repository.save(User.builder().name("Inactive").active(false).build());
List<User> active = repository.findByActiveTrue();
assertThat(active).hasSize(1);
}
}
```
### Custom Queries
```java
@Test
void shouldExecuteCustomQuery() {
repository.save(new User("John", "[email protected]"));
repository.save(new User("Jane", "[email protected]"));
List<User> users = repository.findByEmailDomain("example.com");
assertThat(users).hasSize(2);
}
```
## WebEnvironment Options
| Option | Server | Use Case |
|--------|--------|----------|
| `MOCK` | No | MockMvc testing |
| `RANDOM_PORT` | Yes, random port | Full integration |
| `DEFINED_PORT` | Yes, configured port | Specific port needed |
| `NONE` | No | Non-web testing |
## Test Properties
### Inline Properties
```java
@SpringBootTest(properties = {
"spring.datasource.url=jdbc:h2:mem:test",
"logging.level.org.springframework=DEBUG"
})
class TestWithProperties {
}
```
### Profile-based
```java
@SpringBootTest
@ActiveProfiles("test")
class TestWithProfile {
}
```
### application-test.yml
```yaml
spring:
jpa:
show-sql: true
properties:
hibernate:
format_sql: true
sql:
init:
mode: always
```
## Common Assertions
### Response Body
```java
.andExpect(jsonPath("$.name").value("John"))
.andExpect(jsonPath("$.items").isArray())
.andExpect(jsonPath("$.items", hasSize(3)))
.andExpect(jsonPath("$.items[0].name").value("Item 1"))
.andExpect(jsonPath("$.total").value(greaterThan(0)))
```
### Headers
```java
.andExpect(header().string("Content-Type", "application/json"))
.andExpect(header().exists("X-Custom-Header"))
```
### Status
```java
.andExpect(status().isOk()) // 200
.andExpect(status().isCreated()) // 201
.andExpect(status().isNoContent()) // 204
.andExpect(status().isBadRequest()) // 400
.andExpect(status().isUnauthorized()) // 401
.andExpect(status().isForbidden()) // 403
.andExpect(status().isNotFound()) // 404
```
## Anti-Patterns
| Anti-Pattern | Why It's Bad | Solution |
|--------------|--------------|----------|
| Using @SpringBootTest for unit tests | Extremely slow | Use @ExtendWith(MockitoExtension.class) |
| Hardcoding ports | Port conflicts | Use webEnvironment = RANDOM_PORT |
| Using H2 for DB-specific features | False confidence | Use Testcontainers with real DB |
| No data cleanup between tests | Tests interfere | Use @Transactional or manual cleanup |
| Not using @ServiceConnection | Manual configuration | Let Spring auto-configure from container |
| Testing with production profile | Dangerous side effects | Use @ActiveProfiles("test") |
| Ignoring test execution time | Slow CI/CD | Optimize with slice tests, parallelize |
## Quick Troubleshooting
| Problem | Likely Cause | Solution |
|---------|--------------|----------|
| Tests very slow | Full context for everything | Use slice tests where possible |
| "Port already in use" | Hardcoded port | Use RANDOM_PORT |
| Flaky tests | Shared state or timing | Isolate data, use @Transactional |
| "Bean not found" | Wrong context configuration | Check @Import or component scan |
| Container won't start | Docker not running | Start Docker daemon |
| "Connection refused" | Wrong host/port | Use container.getHost(), getMappedPort() |
## Reference Documentation
- [Spring Boot Testing Reference](https://docs.spring.io/spring-boot/reference/testing/)
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.