3 ms·

Those tests are helpful when you do major architectural changes, which may not happen every year. Tests also help in general development. Make some changes, th

by acchow 7y ago

Those tests are helpful when you do major architectural changes, which may not happen every year. Tests also help in general development. Make some changes, then fix the tests. If you are running tests locally on your machine (and offline) how can you be sure that every time a test fails locally the failure is logged?

kazinator 7y ago
... and you don't always know what is a "major architectural change" that's going to break one of these tests, so you can't just relegate those tests into a category that is only run for major architectural changes.
war1025 7y ago
There's a difference between tests that haven't broken because they are in stable code, and tests that haven't failed because they are testing tautologies or even just completely failing to break when the underlying code is broken. I've lost count of how many times I've gone into an old test suite at work and found that the tests were still passing even though the code they were testing had completely changed or been removed. Sometimes tests are written very poorly. The codebase benefits from their removal.