No tests found
Part of Testing & CI, which counts for 10% of the overall score. When this check fires it deducts 15 points from that category, once per scan, no matter how many places it turns up.
What it detects
No files matching common test naming conventions (*.test.*, *.spec.*, tests/, test_*.py) were found anywhere in the project.
Why it matters
With zero tests, the only way you learn a change broke signup, checkout, or a data write is when a real user hits the broken path. That failure mode gets worse with AI-assisted editing, because an agent will confidently rewrite behavior nothing ever verifies. Even a small suite over the riskiest functions turns silent regressions into a red test run before deploy.
How to fix it
Pick a runner and write your first tests today: Vitest or Jest for JS/TS (files named *.test.ts next to the source), pytest for Python (tests/test_*.py). Start with the highest-risk code, anything touching money, auth, or persistent data, and test pure logic first since it needs no mocking. Wire the runner into the "test" script in package.json (or a Makefile target for Python) so one command runs everything, then add that command to CI.
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