3 ms·
>Did I fail to mention something? Yep. Integration tests under "top level system test" and above "tightly coupled unit tests" are not only excellent at catchin
by crdoconnor 10y ago
>Did I fail to mention something?
Yep. Integration tests under "top level system test" and above "tightly coupled unit tests" are not only excellent at catching bugs in integration code, they don't require hours of tedious mocking and don't have to be completely rewritten when you refactor the code base.
>No one dares to refactor anything
Is a problem on heavily unit tested code. Unit tested = tests that are tightly coupled to the code = refactoring turns the tests red whether or not anything was broken = people prefer leave the code alone.
- gonvaled 10y agoDon't agree. Refactoring does not mean that you need to refactor the tests, but that you will be testing other pieces. That is, when you refactor the old pieces are still there (in the libraries), and their tests still work, but you are maybe not using them anymore higher up in the hierarchy.