3 ms·
I just took a peice of code with quite good test coverage, and stopped running main a couple of times during the "unit" test run. Coverage plumetted, and I real
by tehwalrus 10y ago
I just took a peice of code with quite good test coverage, and stopped running main a couple of times during the "unit" test run. Coverage plumetted, and I realised how much of the code is still untested.
(The code was actually already structured for testing, I just hadn't written them because of that coverage number....)
I am still running main, by the way, but that's a different invocation called "system tests" which runs if unit tests pass (and after the coverage report).
- aisofteng 10y agoThis is a prime example of why not to covet code coverage figures. They can never be taken at face value as an indicator of testing quality or comprehensiveness. Incidentally, OP, I empathize - I had to learn it the hard way too.