I installed the trial version of Clover some days ago, according to the directions in the installation guide. Then I marked my project as a clover-enabled project. Whenever I run some simple test from my src/test/java directory (it's an imported maven project) I hope to see the test included in the test contributions view, but it doesn't happen. No matter what I try: the 4 clover views (Coverage explorer, Test run explorer, test contributions, clover dashboard) remain empty. Is it related to my project using aspectj (I read somewhere clover and aspectj don't go along well), or am i missing something simple?
Clover does not support AspectJ (unless you have AspectJ and Java source files fully separated, i.e. no AspectJ annotations in Java).
How did you import your Maven project into Eclipse? How do you run build and tests? Using Maven command or using Eclipse builder? Please note that Clover requires that "Java builder" is used (you can check it in project's properties).
Do you keep application and test code in the same project?
Thanks for your response!
1) Clover does not support AspectJ: that's a showstopper for my evaluation, as we shouldn't have to change our architecture to be able to run a coverage tool
2) How did you import your Maven project into Eclipse?
Did a 'mvn clean install' on a command line, and used 'import maven project' from the file menu in eclipse
3) How do you run build and tests? Using Maven command or using Eclipse builder? Please note that Clover requires that "Java builder" is used (you can check it in project's properties).
I see 3 builders: Aspectj builder, Maven Project Builder and Clover No-java builder
4) Do you keep application and test code in the same project?
We have a separate test project containing the integration and system tests. To evaluate clover I started by using some small unit tests included in the same project, but even those didn't produce anything
As described in the "Instrumenting+RCP+Application" manual, the trick is to run <clover-instr/> in order to produce an instrumented version of Java sources and to put them into another workspace, keeping the original directory structure as well all non-java files you'd normally need (resources for example).
As Clover instrumentation in based on the source code and not on the byte code (as Cobertura or Emma does, for instance), such instrumented sources should be "transparent" for AspectJ (because they look just like the normal source code, but a just more complex).
Thanks to this, you shall be able to compile such instrumented sources using AspectJ. As soon as such instrumented code will be executed, Clover's coverage recorders should start recording code coverage.
Please let me know at which point exactly from this manual you got stuck.
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs