Hacker News Reader

I understand the underlying message but I prefer the equivalent following phrasing: "check test suite coherence".

It moves the deletion as a means towards the coherence rather than as an end in and of itself, and also includes refactoring as an option.

I hope it helps the less experienced developers grab the intention more explicitly.

I think the core point isn't about coherence, but tradeoffs. Some tests are not worth holding onto: ones that are slow, flaky, and test code that is of marginal importance. In those cases, the ideal tradeoff can be to delete the test. Perhaps to rewrite a better one, or perhaps to just 'eat' the risk incurred by removing it in favor of improved iteration times and the other long term benefits of not having to maintain it.

As always, mentioning that Your Mileage May Vary (YMMV) puts the emphasis/decision on the people facing this or that situation rather than blindly applying advice found on the Internet.

And rightfully so :)

This is being down-voted, but there is merit to this. Tests should be audited for continued need.

Can one configure tests to run in “full”, “actual” and “scope:<modname>” modes?

Also just deleting dead code and tests that go along with it

Tend to get a boost in application boot/startup time, too