This is exactly the point - because of the fact that test classes were not instrumented by Clover, Clover has no information about tests which were executed. That's why you see a "No test result could be found" message in the HTML report.
Pleae note that there's a possiblity to use JUnit's XML test result files. This is useful in case you're using a test framework not recognized by Clover. You have to use the <testresults> option of the <clover-report> task.
But unfortunately ... you still have to instrument your test classes (sic! but you can treat them as application classes i.e. to not record per-test coverage for them) ... the point is that Clover must attach test result from JUnit's XML file to a certain class and this class must exist in Clover's database.
Hi Marek! Even if I instrument the tests I can t see them in the report. Here it s how I define where the tests are located :
<include name="*.java" />
<include name="**/*.java" />
Any obvious thing I m doing wrong please? Is there a way to debug if clover found any tests using the specified path? Thanks for all your help!
Over the next several weeks we'll be sharing some of our Getting Started guides here in the community. Throughout this series of posts, we'd love to hear from customers and non-customers ab...
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