I think that would be interesting to have the ability to filter methods from the coverage report. There are methods that aren't important (for a lack of a better adjective) enough to be tested. For example, if I override a toString() method for debug purposes, or dummy get/set methods. The problem is that the coverage report is polluted from non-tested code that from a developer point of view shouldn't be tested (well, just simply not interested in test it).
Log in to post a comment.