Preventing JUnits from having methods interferes with emma

[dgradl]

Curious to see the code that is executed (covered) by my Cucumber tests I attempted to run a code coverage analysis with Emma (eclemma to be more specific - i.e. the eclipse plugin). It seems that it must be doing some augmentation of the test classes and introducing its own methods, because when I attempted to run this against my Cucumber JUnits it failed with the error message: Classes annotated with @RunWith(Cucumber.class) must not define any methods.

Yea its sort of an edge case. I'm not even sure that code coverage via Cucumber is a metric that is meaningful. However, I'm also not sure if the Cucumber runner needs to be so strict about preventing methods on the JUnit runner. Perhaps it should just prevent JUnit annotated methods from being on the JUnit class.

[aslakhellesoy]

Dupe of #258, which was fixed in 1.0.0.RC23.

See https://github.com/cucumber/cucumber-jvm/blob/master/History.md

Please always report what version you are using - now I just have to guess that you're using something < 1.0.0.RC23.

[dgradl]

1.0.0.RC21. Will do better review prior to opening.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.