2 ms·
Your test suite consists of neatly arranged files containing fully independent functions, and it is separated from your production source tree. The only reason
by tinco 13y ago
Your test suite consists of neatly arranged files containing fully independent functions, and it is separated from your production source tree.
The only reason it could ever be a burden is that the tests take a lot of time to run. In which case you could see if there's anything you could optimize, perhaps only run parts of your suite at any time.
- collyw 13y agoAnd making sure that your tests are correct. I seem to spend as much time messing about until the tests work, as I do on the code it is testing.
- mantrax4 13y ago> "Your test suite consists of neatly arranged files containing fully independent functions" They're not independent. They depend on the code being tested. This isn't a problem for well chosen & well made tests (i.e. testing precisely interfaces and behavior that are intended to remain the same from release to release). But due to various religious practices, most of the tests I've seen aren't like that. Instead, they're tightly coupled to the implementation of an app, which makes refactoring harder, not easier.