Testing in prod is a power move honestly. Rock star-level

Ah yes. The unintended consequences of mandated code coverage without reviewing the tests. If you can mock the shit out of the test conditions to always give you exactly the answer you want, what's the point of the test?

It's like being allowed to write your own final exam, and all you need to pass the exam is 90% correct on the questions you wrote for yourself.

Unit tests, yes, but you don't only do unit tests. Integration and e2e tests still exist.

And this is why mocks are bad…

We build systems to manage day care licenses in the state instead of buying someone else’s product.

Still waiting on approval for more resources. It's not a priority in the company.

I swear we have like 4 runners on a raspberry pi.

My test suite takes quite a bit of time, not because the code base is huge, but because it consists of a variety of mathematical models that should work under a range of conditions.

This makes it very quick to write a test that's basically "check that every pair of models gives the same output for the same conditions" or "check that re-ordering the inputs in a certain way does not change the output".

If you have 10 models, with three inputs that can be ordered 6 ways, you now suddenly have 60 tests that take maybe 2-3 sec each.

Scaling up: It becomes very easy to write automated testing for a lot of stuff, so even if each individual test is relatively quick, they suddenly take 10-15 min to run total.

The test suite now is ≈2000 unit/integration tests, and I have experienced uncovering an obscure bug because a single one of them failed.