Exactly! You actually CAN have 50 people finish something 50x faster, but it takes a shitload of planning, and that equals time and money no company I have ever worked for, or even known of, would allocate to something that isn’t generating immediate income.

Take the Hoover Dam for example: Dsigned over 3 ish years and built in 5, at a time when nothing that huge had ever been made before, at less than a billion in today money, and 2 years ahead of schedule. It’s 90 years old.

That’s why the cat is smug. It knows you know this.

A repo dedicated to non-unit-test tests would be the best way to go. No need to pollute your main code repo with orders of magnitude more code and junk than the actual application.

That said, from what I understand of the exploit, it could have been avoided by having packaging and testing run in different environments (I could be wrong here, I’ve only given the explanation a cursory look). The tests modified the code that got released. Tests rightly shouldn’t be constrained by other demands (like specific versions of libraries that may be shared between the test and build steps, for example), and the deploy/build step shouldn’t have to work around whatever side effects the tests might create. Containers are easy to spin up.

Keeping them separate helps. Sure, you could do folders on the same repo, but test repos are usually huge compared to code repos (in my experience) and it’s nicer to work with a repo that keeps its focus tight.

It’s comically dumb to assume all tests are equal and should absolutely live in the same repo as the code they test, when writing tests that function multiple codebases is trivial, necessary, and ubiquitous.

It’s not uncommon to keep example bad data around for regression to run against, and I imagine that’s not the only example in a compression library, but I’d definitely consider that a level of testing above unittests, and would not include it in the main repo. Tests that verify behavior at run time, either when interacting with the user, integrating with other software or services, or after being packaged, belong elsewhere. In summary, this is lazy.

The P in Prod stands for “It’ll be Pfine”

10 minutes for a process is essentially infinity