Will It Vibe?No Spring Boot integration test found
Part of Testing & CI, which counts for 10% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
This looks like a Spring application (it has at least one @RestController/@Controller/@Service/@Component) but no test anywhere uses @SpringBootTest, so the application context, bean wiring, and auto-configuration are never actually verified to boot together. Unit tests on individual classes do not catch a broken bean graph.
Why it matters
This looks like a Spring application with real controllers, services, or components, but no test anywhere uses @SpringBootTest, so the full application context, bean wiring, and auto-configuration are never verified to actually boot together. Plain unit tests on individual classes do not catch a missing bean, a misconfigured property, or a circular dependency that only shows up when the whole context starts.
How to fix it
Add at least one @SpringBootTest-annotated test (even a minimal "contextLoads" test with no assertions) so CI fails fast if the application context cannot start, then grow it into a small number of integration tests covering the app's critical wiring.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo