Source code
Code quality
Stability
No automated tests in an app repo
Part of the Engineering practices check · fix arrives as a guide
What it is
The repository builds and deploys an application but contains no test files and no test runner configured to run them.
Why it matters
Nothing catches a regression before your users do. Every change is verified by whoever wrote it, once, by hand — which is fine until the change is a small one nobody thought needed checking.
How to fix it
Start with the paths where a silent break is most expensive: authentication, payments, and anything that writes to the database. A handful of tests over those is worth more than broad coverage of view code.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.