a-pavithraa/springboot-skills-marketplace / plugins/springboot-architecture/skills/writing-springboot-tests
writing-springboot-tests
VerifiedUse when writing or adding tests or integration tests for Spring Boot code at a service's edges: HTTP clients that call other services (WireMock: 4xx and 5xx responses, timeouts, retries), Kafka or RabbitMQ listeners (redelivery, poison messages, dead-letter topics), events published to other services, or full-API tests against real databases with Testcontainers; domain logic whose rules must hold for every input (calculations, value objects, state transitions, parsing and formatting), tested as properties over generated inputs; also when a Boot 4 test needs the right imports, slices or container wiring. Supplies verified Boot 4.1 templates and the framework traps that make such tests pass without proving anything. Not for reviewing existing tests (see code-reviewer) or Boot 3 to 4 test migration (see springboot-migration).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.9 KB |
| assets/api-integration-test.java | other | 5.1 KB |
| assets/event-publication-test.java | other | 6.2 KB |
| assets/http-client-wiremock-test.java | other | 6.9 KB |
| assets/message-listener-test.java | other | 6.6 KB |
| assets/personas-db.java | other | 1.8 KB |
| assets/personas-jwt.java | other | 2.3 KB |
| assets/personas-oidc.java | other | 2.9 KB |
| assets/pitest-plugin.xml | config | 1.2 KB |
| assets/property-test.java | other | 4.6 KB |
| assets/repository-slice-test.java | other | 2.6 KB |
| assets/route-access-test.java | other | 4.4 KB |
| assets/service-unit-test.java | other | 5.4 KB |
| assets/testcontainers-configuration.java | other | 2.4 KB |
| assets/webmvc-slice-test.java | other | 4.3 KB |
assets/api-integration-test.java
View on GitHubpackage {{PACKAGE}}.orders;
import {{PACKAGE}}.TestcontainersConfiguration;
import com.github.tomakehurst.wiremock.WireMockServer;
import org.junit.jupiter.api.Test;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.boot.resttestclient.autoconfigure.AutoConfigureRestTestClient;
import org.springframework.boot.test.context.SpringBootTest;
import org.springframework.context.annotation.Import;
import org.springframework.http.MediaType;
import org.springframework.test.context.jdbc.Sql;
import org.springframework.test.web.servlet.client.RestTestClient;
import org.wiremock.spring.ConfigureWireMock;
import org.wiremock.spring.EnableWireMock;
import org.wiremock.spring.InjectWireMock;
import static com.github.tomakehurst.wiremock.client.WireMock.*;
import static org.assertj.core.api.Assertions.assertThat;
import static org.springframework.boot.test.context.SpringBootTest.WebEnvironment.RANDOM_PORT;
/**
* Over a real port: the whole service, its real database in a container, real HTTP in and out.
* Other services (here the payment provider) are WireMock stubs: we own neither their code nor their uptime.
* In a service that talks to others, most tests look like this; in a monolith, keep a few for critical paths.
*
* @Transactional does NOT roll back here: the server commits on its own thread. The @Sql scripts reset the
* data before each test, so tests don't depend on order. WireMock stubs are reset after each test.
*
* Test dependency: org.wiremock.integrations:wiremock-spring-boot (not managed by Boot; 4.4.3 runs on Boot 4.1).
*
* A random-port request can't sign in through a browser login (oauth2Login with a server-side session). For routes
* behind one, drop RANDOM_PORT and RestTestClient, add @AutoConfigureMockMvc, and send requests through MockMvcTester
* as a persona (personas-oidc.java). The rest of this setup stays.
*/
@SpringBootTest(webEnvironment = RANDOM_PORT)
@AutoConfigureRestTestClient
@Import(TestcontainersConfiguration.class)
@EnableWireMock(@ConfigureWireMock(name = "payments", baseUrlProperties = "payments.base-url"))
@Sql({"/sql/reset.sql", "/sql/products.sql"}) // products.sql: P-1 "Arc lamp", price 12.50, stock 10
class PlaceOrderApiTest {
@Autowired
RestTestClient client;
@InjectWireMock("payments")
WireMockServer payments;
@Test
void placesAnOrderChargesItAndReducesTheStock() {
payments.stubFor(post("/charges").willReturn(okJson("""
{"chargeId": "ch_1", "status": "CAPTURED"}
""")));
String location = client.post().uri("/api/orders")
.contentType(MediaType.APPLICATION_JSON)
.body("""
{"productCode": "P-1", "quantity": 3}
""")
.exchange()
.expectStatus().isCreated()
.expectBody()
.jsonPath("$.total").isEqualTo(37.50) // 3 x 12.50 from products.sql
.jsonPath("$.status").isEqualTo("PLACED")
.returnResult()
.getResponseHeaders().getLocation().toString();
client.get().uri(location)
.exchange()
.expectStatus().isOk()
.expectBody().jsonPath("$.quantity").isEqualTo(3);
client.get().uri("/api/products/P-1")
.exchange()
.expectBody().jsonPath("$.stock").isEqualTo(10 - 3); // the side effect, seen from outside
// What went over the wire to the provider, as the provider's API documents it
payments.verify(postRequestedFor(urlEqualTo("/charges"))
.withRequestBody(equalToJson("""
{"reference": "${json-unit.any-string}", "amount": 37.50}
"""))); // numbers compare as numbers: 37.5 matches 37.50
}
@Test
void refusesAnOrderLargerThanTheStockWithoutCharging() {
client.post().uri("/api/orders")
.contentType(MediaType.APPLICATION_JSON)
.body("""
{"productCode": "P-1", "quantity": 11}
""")
.exchange()
.expectStatus().isEqualTo(422)
.expectBody().jsonPath("$.detail").value(String.class, detail -> assertThat(detail).contains("P-1"));
client.get().uri("/api/products/P-1")
.exchange()
.expectBody().jsonPath("$.stock").isEqualTo(10);
payments.verify(0, postRequestedFor(urlEqualTo("/charges")));
}
@Test
void aDeclinedPaymentRollsBackTheStockReservation() {
// The failure only a test with the real database can see: does the whole transaction roll back?
payments.stubFor(post("/charges").willReturn(aResponse().withStatus(402)));
client.post().uri("/api/orders")
.contentType(MediaType.APPLICATION_JSON)
.body("""
{"productCode": "P-1", "quantity": 3}
""")
.exchange()
.expectStatus().isEqualTo(422);
client.get().uri("/api/products/P-1")
.exchange()
.expectBody().jsonPath("$.stock").isEqualTo(10);
}
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |