Delete tests

(andre.arko.net)

125 points mooreds | 1 comments | 27 Aug 25 11:18 UTC | HN request time: 0.2s | source

Show context

vitonsky ◴[30 Aug 25 06:38 UTC] No.45072400[source]▶

No, thanks. I already spent time to write tests while implementing a features, now I have a lot of tests that proof the feature is works fine, and I no more fear to make changes, because tests keep me safe of regression bugs.

The typical problems of any code base with no tests is a regression bugs, rigid team (because they must keep in mind all cases when code may destroy everything), fear driven development (because even team with zero rotation factor don't actually remember all problems they've fixed).

replies(1): >>45072478 #

willio58 ◴[30 Aug 25 06:55 UTC] No.45072478[source]▶

>>45072400 #

Did you read the article?

What is your answer to the points the author makes around flaky tests/changing business requirements/too many tests confirming the same functionality and taking too long to run?

replies(3): >>45072603 #>>45072615 #>>45072625 #

1. snovv_crash ◴[30 Aug 25 07:22 UTC] No.45072615[source]▶

>>45072478 #

Flaky tests: tests should be deterministic. If your tests are flakey in a 100% controlled environment, probably your real system is unreliable too.

Changing business requirements: business logic should be tested separately. It is expected to change, so if all of your tests include it, then yes of course it will be hard to maintain.

Too many tests for the same thing: yeah then maybe delete some of the duplicates?

Taking too long: mock stuff out. Also, maybe reconsider some architectural decisions you made, if your tests take too long it's probably going to bother your customers with slow behaviour too.

↑