Ugh, another discussion about tests and the person wants to remove all "destroy tables at the end of the test" step, 'cause "tests are slow".

If your tests are slow, your system is slow. Fucking up tests won't solve this.

Oh, {deity}.

"I want to increase coverage, but with those slow tests, it is impossible."

I mean, this is all the sort of trigger warning I have about tests...

(The ones that always gets me in trouble 'cause "the internet says it is not so".)

I'm so happy this whole discussion have nothing to do with my project.


My project currently have only 44% coverage, although I'm pretty sure it says absolutely nothing 'cause there are still thousands and business rules that don't have tests -- only tests going through the lines of code, which says nothing.

But going from 0% to 44% gives me enough hope to actually put MyPy to check types now.

@juliobiason What you said about business rules is important. Business rules should have tests

Sign in to participate in the conversation
Functional Café

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!