7 ms·

Unless your test suite needs a rewrite, as well… (Better refactor, of course)

• camgunz 8y ago
  Your test suite should essentially be your requirements. If it's out of date, it's the first thing you should update. Adding features or changing your requirements without updating your tests is the essence of tech debt: you're delivering features quickly at the expense of future work and brittleness. I agree it's pretty common though. I've also seen huge test suites of only unit tests, no integration tests. As a result, you have no assurance that your refactors work because changing the inner workings fundamentally requires you to change the unit tests too, and nothing checks the top-level interface.
• Shorel 8y ago
  You either rewrite the tests, or the code. Not both at the same time, in my opinion.