re: When Not to Add Unit Tests VIEW POST

re: I would agree in the situation where the units of code that you are testing have some minimum amount of encapsulation and separation of concerns. I...

If refactoring breaks your tests means either your tests are fragile or your code is not SOLID. Let's not confuse refactoring with change requests

Sometimes it is the interaction and interface between functions and classes that need refactored. It is of no benefit to add a unit test to an interface which does not isolate concerns, provide abstraction, or encapsulation only to then refactor that interface.

Exactly.. if the code follows the SOLID principles, it's easier to write tests that won't break at the smallest code change.

Code of Conduct Report abuse