The only way I have found to not check code coverage on my JUnit tests is to right click on the package, choose Coverage as..., and then choose configuration. Then I can unclick my test package. I have tried every possible combination to exclude test under the general preferences/java/code coverage/exclude and not seen any changes. I always put my tests in a separate test source folder with the same package name as my src code.
Do I really have to configure every single project to ignore my JUnit tests? This seems redundant. Why would anyone want to check the coverage of their tests?
ECLEmma just excludes those files which are excluded , but it does not create creating coverage report and giving 0% coverage for that file , generating report
Finally ECL Emma not supporting this.
There is option
Only path entries matching
inPreferences -> Java -> Code Coverage
that is described in documentation at http://www.eclemma.org/userdoc/preferences.html:After setting it to
src/main/java
and running test that is located insrc/test/java
: