- changing code
- running tests with coverage
- final result: all fine
But that's (sometimes) not true because:
- I'm using coveralls.io and it says (as example) that I have a coverage of 94.708%
- in coverage.py I can say
--fail-under=95and the coverage doesn't fail because it obviously does rounding to an integer.
It's a bit uncomfortable when you run all things locally before you commit your changes but finally fail because of such an issue. It happens to me several times.
I see following essential improvements you could do:
- enable to define precise coverage for
- displaying precise coverage
Thomas (mail: firstname.lastname@example.org)