3 ms·
its the same concept as minimizing the amount of code through design and refactoring. Let the tests drive the code, refactor, and refactor / delte your tests w
by keithnz 7y ago
its the same concept as minimizing the amount of code through design and refactoring. Let the tests drive the code, refactor, and refactor / delte your tests when not needed anymore. :)
this is his SO answer where he talks about it... https://stackoverflow.com/questions/153234/how-deep-are-your-unit-tests/153565#153565 https://stackoverflow.com/questions/153234/how-deep-are-your...
- galaxyLogic 7y agoMakes sense. But it does seem like a shift in position from the very "test-centric" view of XP. In the above link I don't see anything about "delete your tests when not needed anymore", or did I miss it? How do you know when some tests are "not needed any more"? Isn't the idea of regression-testing to keep tests around so you know if any new code will break them? That should give you the "agility" to refactor your code, I think, is what the proponents of XP would say.