Trivial/placeholder tests
Part of Testing & CI, which counts for 10% of the overall score. When this check fires it deducts 8 points from that category, once per scan, no matter how many places it turns up.
What it detects
Test files exist but contain very few assertions relative to file count, suggesting scaffolded but unwritten tests.
Why it matters
Test files with almost no assertions pass no matter what the code does, which is worse than having no tests, because the green checkmark builds false confidence in every future change. Scaffolded-but-unwritten tests are a common leftover from project generators and AI coding sessions. Right now your suite is spending CI time verifying close to nothing.
How to fix it
Open every test file and make a call on each: either write real assertions or delete the file so the suite stops overstating itself. A real test calls the code under test with concrete input and asserts a concrete expected output (expect(result).toEqual(...) in Jest/Vitest, assert result == expected in pytest). Remove describe blocks that only contain todos or skipped stubs. Prioritize turning the stubs that cover money, auth, and data-writing code into real tests first.
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