It would be nice to see some option to exclude private methods from the percentage of covered code. I am trying to 100% cover the public methods of an API, but all the private methods are listed there at 0% screwing up my statistics. There are also some public methods which will be removed from the API in future versions so they don't need to be covered, too. I would appreciate to have a feature to tag these "unused" functions so they are not listed in the coverage viewer any longer.

What version of the product are you using? flexcover-0.81

A lot of people have asked for some sort of "tagging" of methods to be excluded and I believe this is very similar in spirit to Issue 9. However, I don't think private methods should be excluded as a blanket option. If you have private methods that are not getting called by your testing, doesn't that mean that one's testing is not exercising the public methods sufficiently?

I agree concerning the private methods. But some sort of tagging would really be fine, for example to exclude methods which are defined in a custom namespace so they aren't accessable to the end user or as i already mentioned for methods which will be removed / changed soon and don't need to be covered.