We are using SonarQube developer edition for our project hosted in GitHub enterprise. So far, we are widely using Sonarqube for our PR and branch. But, we have a challenge that the Unit testing need to be run twice: One in the PR phase and one in the branch merge. In our quality gate, we define the testing coverage is one criterial so we can not skip the testing phase. The UT takes several minutes which causes some latency. Any suggestion from expert here?
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Why don't Unit Test failures show up in short term branches? | 20 | 4401 | June 18, 2024 | |
| An approach to know how frequently developers add automated tests in their codebases | 3 | 303 | January 26, 2024 | |
| Unittests | SLB | 2 | 290 | January 6, 2021 | |
| Best practice for unit and integration tests coverage | 15 | 12496 | March 18, 2021 | |
| Is it mandatory to write CI/CD pipeline for each repo to know the current coverage on PR? | 1 | 368 | March 18, 2021 |