How do I ignore scanning certain classes using EclEmma and Eclipse?

java eclipse eclemma
sdasdadas picture sdasdadas · Jan 21, 2013 · Viewed 14.7k times · Source

I am using EclEmma (inside of Eclipse) to scan my JUnit code coverage. This works correctly - however, I do not want EclEmma to scan my src/view folder since it contains Swing code that I consider not worthy of testing.

Is there any way to ignore this folder when EclEmma runs so that it: a) runs faster, and b) does not skew the coverage percentage?

EDIT:

My project's structure is:

src/view
src/model
src/controller

I have tried these (possibly others) with the Path Entries section in the Preferences page:

"src/view"
"src/view/*"
"view"
"view/*"
src/view

These are using the Excludes section in the Preferences page:

*
*View*
*View*.class
src/view/*View*
src/view/*View*.class

They all leave me with the same result of it analysing my entire src folder.

Answer

mmm111mmm picture mmm111mmm · Dec 2, 2013

[Edit] The maintainers says you cannot, except one the source directory level: https://github.com/jacoco/eclemma/issues/70

I thought eclemma wasn't excluding files: it is. Just not as I thought.

When you go into excludes in preferences and specify your.classes.here.*, for example, that means those classes won't count towards your getting all your code covered, not that those classes won't be included in what needs to be covered by tests.

Try it and see. Try to exclude a class you know have coverage in it. Once you put that to the excludes preference, on a new coverage run they'll still be there in the coverage window, but they'll come up as 0% and will all be in red.

Rather useless if you ask me. I'm still searching for an adequate solution to exclude classes by name from the classes that need to be covered by tests.

Related questions

Eclemma says 1 of 4 branches not covered, but which branch is it?

Is there a simple way to tell which branch I am missing? I.e. I have some code like this: if (x || y) { // do stuff } In the coverage highlighting there is a yellow dot in Eclipse that says: 1 of 4 branches …

Read More
Improve Lombok @Data Code Coverage

I am writing unit tests for my project and am trying to achieve at least 80% code coverage. Problem is that I am using lombok's @Data annotation for generating getters and setters and when I run my unit tests, all those …

Read More
How to exclude classes from the coverage calculation in EclEmma without actually excluding them from the coverage itself

I am using EclEmma to test the coverage of my scenario tests and use case tests on my project. I have a Base package which contains the most general classes and the use case tests. The coverage looks like this: …

Read More