Practice test-driven development for Spring Boot features, fixes, and refactoring.
The material indicates this is essentially a Spring Boot TDD prompt/workflow document, with no required secrets and no declared remote endpoints. Given it is prompt-only, open-source, and has strong community adoption, the overall risk is low; only note that the referenced Testcontainers/testing workflow may lead to local test execution and dependency pulls in real use.
The material explicitly states that no keys or environment variables are required, and the README does not request API tokens, database passwords, or cloud credentials; there is no direct sign of credential collection, storage, or misuse.
Both the system checks and the material show no declared remote endpoints; the skill itself is a prompt/document and does not describe sending user data to third-party services. The README mentions Testcontainers and Maven plugins, which only imply normal dependency/image downloads when users choose to run tests, not abnormal egress by the skill itself.
The audited object is a prompt-only skill; the material provides test examples and workflow guidance, not executable install scripts, automatic commands, or local process control logic. Although it mentions JUnit, MockMvc, SpringBootTest, and Testcontainers, that is methodology guidance and does not mean the skill itself has code-execution privileges.
The material does not request direct read/write access to local files, databases, system directories, or other resources; the data access shown in examples is only illustrative Spring Boot test code and does not show the skill actively reading or exporting user data.
Positive factors include being open-source on GitHub, auditable, and having very high community adoption (~210.5k stars), all of which materially reduce risk. Points to watch are that the repository link does not obviously match the skill name, the license is not declared, and maintenance status is unknown; the README also references third-party dependencies such as Maven, JaCoCo, and Testcontainers, so users should verify repository identity and dependency sources in actual use.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "springboot-tdd" skill from askskill: 1. Download https://raw.githubusercontent.com/affaan-m/ECC/main/skills/springboot-tdd/SKILL.md 2. Save it as ~/.claude/skills/springboot-tdd/SKILL.md 3. Reload skills and tell me it's ready
Use TDD to add a user registration API in Spring Boot: first write failing JUnit 5 and MockMvc tests, then implement the minimum working code, mock dependencies with Mockito, and add key edge-case tests.
A TDD-structured set of test and implementation examples covering controller, service, and edge cases.
Here is a Spring Boot bug: inventory is not restored after order cancellation. First write a failing test that reproduces it, then provide the fix, and explain how to verify with Mockito or Testcontainers that no side effects were introduced.
A regression-oriented solution with bug-reproducing tests, fix implementation, and verification strategy.
I want to refactor a Spring Boot order service by splitting oversized business methods. Design unit tests, integration tests, and JaCoCo coverage goals based on the current behavior to ensure nothing changes after refactoring.
A refactoring-focused testing plan with test layers, coverage targets, and example code structure.
TDD guidance for Spring Boot services with 80%+ coverage (unit + integration).
@ExtendWith(MockitoExtension.class)
class MarketServiceTest {
@Mock MarketRepository repo;
@InjectMocks MarketService service;
@Test
void createsMarket() {
CreateMarketRequest req = new CreateMarketRequest("name", "desc", Instant.now(), List.of("cat"));
when(repo.save(any())).thenAnswer(inv -> inv.getArgument(0));
Market result = service.create(req);
assertThat(result.name()).isEqualTo("name");
verify(repo).save(any());
}
}
Patterns:
@ParameterizedTest for variants@WebMvcTest(MarketController.class)
class MarketControllerTest {
@Autowired MockMvc mockMvc;
@MockBean MarketService marketService;
@Test
void returnsMarkets() throws Exception {
when(marketService.list(any())).thenReturn(Page.empty());
mockMvc.perform(get("/api/markets"))
.andExpect(status().isOk())
.andExpect(jsonPath("$.content").isArray());
}
}
@SpringBootTest
@AutoConfigureMockMvc
@ActiveProfiles("test")
class MarketIntegrationTest {
@Autowired MockMvc mockMvc;
@Test
void createsMarket() throws Exception {
mockMvc.perform(post("/api/markets")
.contentType(MediaType.APPLICATION_JSON)
.content("""
{"name":"Test","description":"Desc","endDate":"2030-01-01T00:00:00Z","categories":["general"]}
"""))
.andExpect(status().isCreated());
}
}
@DataJpaTest
@AutoConfigureTestDatabase(replace = AutoConfigureTestDatabase.Replace.NONE)
@Import(TestContainersConfig.class)
class MarketRepositoryTest {
@Autowired MarketRepository repo;
@Test
void savesAndFinds() {
MarketEntity entity = new MarketEntity();
entity.setName("Test");
repo.save(entity);
Optional<MarketEntity> found = repo.findByName("Test");
assertThat(found).isPresent();
}
}
@DynamicPropertySource to inject JDBC URLs into Spring contextMaven snippet:
<plugin>
<groupId>org.jacoco</groupId>
<artifactId>jacoco-maven-plugin</artifactId>
<version>0.8.14</version>
<executions>
<execution>
<goals><goal>prepare-agent</goal></goals>
</execution>
<execution>
<id>report</id>
<phase>verify</phase>
<goals><goal>report</goal></goals>
</execution>
</executions>
</plugin>
assertThat) for readabilityjsonPathassertThatThrownBy(...)class MarketBuilder {
private String name = "Test";
MarketBuilder withName(String name) { this.name = name; return this; }
Market build() { return new Market(null, name, MarketStatus.ACTIVE); }
}
mvn -T 4 test or mvn verify./gradlew test jacocoTestReportRemember: Keep tests fast, isolated, and deterministic. Test behavior, not implementation details.
Audit Claude skills and commands with quick scans or full stocktakes.
Create iOS liquid glass interfaces with dynamic visuals and interactive morphing.
Record polished web app UI demo videos for walkthroughs, tutorials, and showcases.
Plan demand forecasts, safety stock, and replenishment for multi-location retail inventory.
Unify multi-channel notifications for routing, deduplication, escalation, and inbox consolidation.
Audit, plan, and implement SEO improvements for better search visibility.
Apply test-driven development to Quarkus 3.x features, fixes, and refactors.
Build features, fix bugs, and refactor code with test-driven development.
Build robust Django tests with pytest-django, TDD, mocks, factories, and API coverage.
Generate Spring Boot code, audit security, and optimize application queries.
Implement features and fixes by writing tests before production code.
Use test-first development to improve code quality and maintainability.