I don't think it is common practice to look include the test coverage of the test case. This would blur the coverage figures of your actual production code (test code would typically show nearly 100% if executed). Therefore at least the default behavior shouldn't be changed.

EclEmma by default reports coverage on all files simply because there is no convention for Eclipse projects to locate test code.

I agree with @marchof . But maybe indeed should be possible to do this, however this should be realised as opt-in instead of opt-out. For example in IntelliJ IDEA there is an option to show coverage in code of tests, which is disabled by default.

Thanks replies :)

EclEmma by default reports coverage on all files simply because there is no convention for Eclipse projects to locate test code.

I created a sample code for jacoco's report. It has enough maven convention and the report is divided by package name space (not blur).
https://bitbucket.org/twopack/jacoco-sample
http://4.bp.blogspot.com/-ti_-sVQwWOs/UXOpGo0lt-I/AAAAAAAAPag/oNNh7p4D7zk/s1600/coverage4.png

I cannot judge its common or not. And I absolutely agree blur coverage is bad.
I'll try to change the request to opt-in style with default disabled. So this request is closed.

It has enough maven convention and the report is divided by package name space (not blur).

I'm sorry to miss understanding... I recognized reason of EclEmma by default reports coverage on all files.