JaCoCo : Offer way to merge code-coverage unit vs. it-tests

Hi Manuel,

I've made an implementation to calculate Total Code Coverage, but unfortunately it doesn't work because of Sonar limitation - see SONAR-1914. So, here is a patch for this feature, but I'll come back to it later.

+1 from me on this issue!

I'm migrating Metawidget to Maven/Jenkins/Sonar/JaCoCo. There are lots of advantages, but I'm missing the combined unit/it test coverage I used to get from Emma.

Richard.

Hi guys,

Is there any update on this issue? I'd still love to see it!

Richard.

seems like issue that this one depended upon has been already solved.
I believe that solution for this should be possible now.
Any idea about timeline?

Would love to be able to upload separate project results for both from Cobertura and see as separate and merged info this would be great. My current understanding is cobertura is not supported for it-test coverage ?

Indeed Daniel, we focus our effort on Jacoco because Jacacoco is more suitable to compute code coverage by integration tests as you don't need to deploy a dedicated artifact with instrumented bytecode (this is done on the fly with Jacoco).

For now, in my company we use the jacoco ant merge task to compute this total coverage and is passed to sonar as ITs coverage. We get total coverage in Sonar but we lose real ITs coverage.
This new built-in feature will be a blessing.

@David, could you :

• Remove the widget "All tests coverage" and add the "Overall coverage" section to the existing "Integration tests coverage" widget -> two columns
• Configure the metrics merged_XXXX to automatically display the "Coverage" tab when opening the source viewer
• The section "On new code" doesn't seem to be computed both on "Integration test coverage" and "Overall coverage"
• Rename "Integration test coverage" into "Integration tests coverage"
• Refactor the coverage tab of the code viewer according to the attached screenshot
• Rename the widget "Code Coverage" into "Unit tests Coverage"
• rename the metrics merges_XXX into overall_XXX

just my 2c but one good way to illustrate this nice new feature would be to provide a sample project that demonstrate how all this is configured.

Done

IT modified for overall coverage

Should be the last iteration David :

• The second column in the integration tests coverage widget is badly aligned with the other widgets (see attached screenshot)
• The metric new_id_lines_to_cover and new_overall_lines_to_cover should not be displayed anymore in the integration tests coverage widget (see attached screenshot). This is something which was already done in the unit tests coverage widget.
• There are some missing translations on new_overall_lines_coverage and new_overall_branch_coverage metrics (see attached screenshot)
• When doing a drilldown on "new_***" metrics, the old header of the code viewer is displayed instead of displaying the new one. Moreover I think we should fully remove this old code header.
• In the new Code viewer header, I was wrong by suggesting to use UTs and ITs but let's have a call to discuss this

done

Almost David :

• Drilldown by "new_***" metrics doesn't lead to automatically select the suitable filter in the "Coverage" tab. For instance when drilldowning on the "New IT Coverage" I expect to have a filter on "IT Lines to cover" but I get the default one on "Lines to cover"
• Could you slightly update the coverage header in the code viewer to remove/add some spaces as follows :

  53.3%		Line coverage:	 63.6% (7/11)	Branch coverage:    25.0% (1/4)
  

Fixed the second point. For the first one, I'm not sure I understand what it should do because the metric selector never let the user choose new_*** metrics. Need to talk about it

fixed

Manually tested !

IT added