Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set up code coverage and quality analysis using Sonarqube #1533

Open
5 of 10 tasks
carlspring opened this issue Oct 16, 2019 · 1 comment · May be fixed by strongbox/strongbox-parent#63 or #1682
Open
5 of 10 tasks

Set up code coverage and quality analysis using Sonarqube #1533

carlspring opened this issue Oct 16, 2019 · 1 comment · May be fixed by strongbox/strongbox-parent#63 or #1682
Assignees
Labels
in progress work is in progress

Comments

@carlspring
Copy link
Member

carlspring commented Oct 16, 2019

Task Description

This is the master task for setting up code coverage and quality analysis using Sonarqube.

Tasks

The following tasks will need to be carried out:

Code coverage tasks:

  • Get code coverage and code quality analysis to work with JaCoCo:
    • Get unit tests executed with the maven-surefire-plugin to produce JaCoCo coverage.
    • Get integration tests executed with the maven-failsage-plugin to produce JaCoCo coverage.
    • Merge the reports and publish them to Sonarqube.
  • The code coverage and quality analysis should be done in a Maven profile and not be .
  • Code coverage in pull requests.
  • PMD/CPD/Findbugs for code duplication and additional analysis.

Apply this to the following projects:

Useful links

Help

@saratbeesa
Copy link
Contributor

saratbeesa commented Nov 15, 2019

@carlspring ,

I checked the parent pom for strongbox project, jacoco configuration is already present in it, as a seperate profile with name coverage. I tried to generate the jacoco coverage by building the project, but for some reason it is not getting generated.

Due to these missing .exec files reporting fails to Codacy server , i think its hitting api.codacy.com service to log these metrics.

I'm currently investigating why the jacoco files are not generated, by analysing the debug output of the build,. I found that the the default-test goal executed by maven doesn't contain the additional arguments that're specific to Jacoco agent. For some reason these parameters are not passed to the JVM that runs the tests.

This ticket has not been updated for over a month now, is anyone still working on it ? Because I found the following tasks are already in place for strongbox repository atleast

  • Get unit tests executed with the maven-surefire-plugin to produce JaCoCo coverage.
  • Get integration tests executed with the maven-failsafe-plugin to produce JaCoCo coverage.
  • Merge the reports

Thanks,
Sarat kumar Beesa.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment