Spring Boot project structure — package-by-feature, record DTOs, Flyway migrations, multi-profile config, actuator, proper test structure
84
76%
Does it follow best practices?
Impact
97%
4.04xAverage score across 5 eval scenarios
Passed
No known issues
{
"instruction": "Mirror the main source tree in the test directory and use slice tests",
"relevant_when": "Agent creates tests for a Spring Boot application",
"context": "Test packages must mirror the main source tree (e.g., src/test/java/com/example/order/ mirrors src/main/java/com/example/order/). This enables package-private access in tests. Use Spring Boot slice tests for speed: @WebMvcTest for controllers (no server), @DataJpaTest for repositories (in-memory DB), and reserve @SpringBootTest for full integration tests only.",
"sources": [
{
"type": "file",
"filename": "skills/springboot-project-structure/SKILL.md",
"tile": "tessl-labs/springboot-project-structure@0.2.0"
}
],
"checklist": [
{
"name": "test-mirrors-main",
"rule": "Test classes are placed in packages that mirror the main source tree structure (same package hierarchy under src/test/java/)",
"relevant_when": "Agent creates test classes in a Spring Boot project"
},
{
"name": "slice-tests-used",
"rule": "Controller tests use @WebMvcTest and repository tests use @DataJpaTest rather than @SpringBootTest for everything",
"relevant_when": "Agent creates controller or repository tests in Spring Boot"
}
]
}evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
skills
springboot-project-structure
verifiers