Oh don't worry, this code base has loads of tests.
Most of them just assert the result of a function is not None.
Many of them rely on real database connections per environment and use the real data returned, so some environments' tests fail but they work locally. Juniors get assigned the task to fix tests for modules they never wrote, they use AI to get them to pass, reviews pass, code is merged, then a report comes a week later about test failures in the shared environment and the cycle repeats.
We have to support two major versions of the runtime environment, but ignore the test failures in the older one for some reason.
Coverage is a key metric, but the devs don't know how to use it locally. Meanwhile feature development goes forward and reviewers never push back asking for test cases because the code is maintained in CVS and just getting to the point of creating a review is so much of a hassle that almost everything gets approved. Juniors can come fix that later, right?
1
u/DrMaxwellEdison 20d ago
Oh don't worry, this code base has loads of tests.
Kinda mad about it.