Menu
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?
695
There is option Only path entries matching in Preferences -> Java -> Code Coverage that is described in documentation at http://www.eclemma.org/userdoc/preferences.html:
Comma separated list of strings that must match with the class path entry. A class path entry matches the filter, if it contains one of the given strings. (e.g. "src/main/java", Default: no filter)
After setting it to src/main/java and running test that is located in src/test/java:
93
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
