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

Add Code Coverage metrics to SonarCloud #195

Merged
merged 2 commits into from
May 20, 2020
Merged

Conversation

msilvagarcia
Copy link
Contributor

Description
PHPUnit generates the Clover coverage files with absolute file paths, and I couldn't find a way to change that. So, instead, I set up a step in the Continuous Integration workflow to clean up the report files after it runs.

Tested scenarios
Code Coverage in SonarCloud with a short-lived branch.

@msilvagarcia msilvagarcia merged commit a18c530 into develop May 20, 2020
@msilvagarcia msilvagarcia deleted the sonarcloud-config branch May 20, 2020 10:49
acampos1916 added a commit that referenced this pull request May 20, 2020
* Update README.md

* Update dependency phpunit/phpunit to v9.0.2

* Update dependency phpunit/phpunit to v9.1.1 (#180)

* remove duplicated classmap (#185)

* fix client types declarations (#186)

* added .gitattributes to remove useless files for production from package (#184)

* Create SECURITY.md

Create a security policy as per GitHub recommendation

* update readme with a link to contact support

* [PW-2387]: IP validation function  (#193)

* [PW-2387]: IP address validation util class

* [PW-2387]: Removing reverse-resolve function

* [PW-2387]: Fixes

* Update composer.lock (#182)

Renovate bot missed this on pull request #180. Manually updated it for now.

Rewrote several tests to make it work.

* Create a GitHub Actions workflow

* Fix PHP CodeSniffer problems

* Fix PHP CodeSniffer problems

* Update SonarCloud settings

* Generate coverage reports

* Fix SonarCloud configuration

* Improve reporting relevancy

* Update dependency squizlabs/php_codesniffer to v3.5.5 (#187)

* Update dependency phpunit/phpunit to v9.1.4 (#191)

* Version bump to 6.2.0

* Update README.md

* Add Code Coverage metrics to SonarCloud (#195)

PHPUnit generates the Clover coverage files with absolute file paths, and I couldn't find a way to change that. So, instead, I set up a step in the Continuous Integration workflow to clean up the report files after it runs.

Co-authored-by: Alessio Zampatti <[email protected]>
Co-authored-by: Renovate Bot <[email protected]>
Co-authored-by: cyattilakiss <[email protected]>
Co-authored-by: Vitaliy Ryaboy <[email protected]>
Co-authored-by: Marcos Garcia <[email protected]>
Co-authored-by: Rik ter Beek <[email protected]>
Co-authored-by: marcoss <[email protected]>
@sonarcloud
Copy link

sonarcloud bot commented May 22, 2020

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants