2 ms·
Having 100% code coverage just because is not meaningful in itself, so I don’t see your point. Having 100% is just as not enough because you can arrive at a li
by kaba0 6y ago
Having 100% code coverage just because is not meaningful in itself, so I don’t see your point.
Having 100% is just as not enough because you can arrive at a line of code from exponentially many states. Mutation testing is a good way to show whether the tests are actually worth anything.
- RamblingCTO 6y agoYou misunderstood me. You would need to add tests for getters and setters to guarantee that there's no typo in there (I've seen quite some bugs due to this) but it feels like a waste of time. That's why I'm happy that that's not necessary with kotlin. Code coverage is just a control tool.