Upload coverage data separately and later?

[danlun-pfsw (Daniel Lundqvist)]

For our system we have two types of tests:

1. Unit tests - built and run when software is built.
2. Integration/automated tests - scheduled and run after software is built.

We could probable manage to create coverage data for unit tests in the same pipeline as running the scanner. But the automated tests run for many hours and the build does not wait for its result. Is it possible to upload more results later? Best would be if it could complement data uploaded during scanning.

Based on a few topics like below this does not seem possible currently:

• Separate Coverage for Unit and Integration Tests
• Is it possible to upload test execution and coverage data separately from running sonar-scanner analysis?

Can you say anything about current plans to support this? Of the two, uploading data from integration/automated tests at a later time would for us be more important.

[Colin]

Hey Daniel,

It’s not possible right not to enrich an analysis with more data after something like code coverage is generated.

You may want to join an ongoing similar discussion here.

SonarQube analysis taking too long

I second @ggjulio 's opinion that we should be able to split sonar-scanner in 2 stages: static analysis publishing the results. Ideally we would love to be able to run Sonar in CI pipelines with parallel stages. This would allow us to have our unittests to compile and run in some stages, while sonar is executing the static analysis in multiple stages (one stage per language), the sonar analysis stages then stash the report files and at the end of the pipeline we have a final sonar stage that …

[danlun-pfsw (Daniel Lundqvist)]

Got it, I’ll keep an eye out for this. Hopefully it’s something that you will deliver.