We are seeing report generation take upwards of 4 hours. I'm using the following to generate the html report:
<clover-report coverageCacheSize="2048"> <current outfile="${work.dir}/clover-reports/html" title="Clover HTML Report" alwaysReport="true" showUniqueCoverage="false" summary="false" numThreads="6"> <format type="html"/> <testresults dir="${work.dir}/test-results" includes="TEST-*.xml"/> </current> </clover-report>
The ant process spawning this command is being given 8g for memory. There are a few hundred
unit tests but the project src itself is roughly 2g. Does Atlassian recommend any jvm tuning parameters?
I know that is a bit of a "loaded" , w/ respect to jvm tuning question but for big projects do you guys
have anything which works best in these types of scenarios? Is there a limit to the number of threads
to give this report generation such that it will no longer matter? Any help would be great.
You could try:
Regards
Marek
There is also another option possible - disabling per-test coverage in both instrumentation and reporting. You have to a) override default test detection algorithm by definining an empty expression pattern for test classes in <clover-setup/> or <clover-instr/> task; thanks to this, clover.db***.s coverage files won't be generated, b) disable per-test coverage in <clover-report/> task
Example:
<clover-setup> ... <testsources dir="src/test"> <testclass name="^$"/> </testsources> </clover-setup> ... <clover-report> <current showUniqueCoverage="false"> ... </current> </clover-report>
Drawbacks: a) you will see global coverage only and won't be able to click on a source line to open a pop-up and see which test cases hit certain line; b) you won't see test classes on "Tests" tab and test results in the report.
Cheers
Marek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.