How to force Emma code coverage report to ignore some methods?

Question

Some methods, such as auto-generated getters, setters, equals and toString, are trivial for test. However, if they aren't added into the testing classes, the code coverage percentage (calculated using Emma) is reduced and may crash our system build.

How can I force emma to ignore these methods in the code coverage percentage?

Regards,

Felipe

Dissatisfied

Answer 1

From the EMMA FAQ:

A feature to allow EMMA users to mark arbitrary methods as excluded from coverage is being considered for future versions.

So unfortunately this doesn't seem to be possible at the moment. There's an open feature request for this in EMMA's tracker.

Splendiferous

Any update on this? This answer is almost 3 years old already. – Extremism

Answer 2

I would argue that every bit of code should be covered, including getters and setters, toString, equals and hash code.

I have seen many a pull requests with:

public void setName(String name)
{
   name = name; // instead of this.name = name
}

There are tools out there to help write these cumbersome tests. ToStringVerifier being one, EqualsVerifier being another.

Millimicron