3 ms·
The “benefit” of unit tests telling you exactly where the problem lies is not compelling. All tests should always be passing on master, therefore the problem li
by closeparen 9y ago
The “benefit” of unit tests telling you exactly where the problem lies is not compelling. All tests should always be passing on master, therefore the problem lies in “git diff master.” If you can’t tell where the problem is that’s breaking an integration test, your changeset is too large or there are too many layers of indirection.
Approximately all of the bugs I encounter in real life would have been prevented by integration tests but not unit tests. Unfortunately my organization only believes in unit testing, so 95% of our test code mostly just exercises its own mocks.
- mannykannot 9y ago>95% of our test code mostly just exercises its own mocks. How much time and effort goes into testing and otherwise validating the mocks?
- aeorgnoieang 9y ago> so 95% of our test code mostly just exercises its own mocks Yikes/uggh Unit tests are great for those little ... 'units' that you can feed specific test cases. I've found that the code that needs lots of mocks to be tested is exactly that which is best covered by integration tests.