Note that while measures such as the number of tests are displayed at the project level, no drill-down is available. Path to the directory holding the CPPUnit reports. All languages sonar.testExecutionReportPathsĬomma-delimited list of paths to execution reports in the generic test data format. SonarQube only supports test execution reports for the branches of a project (including the main branch), not for pull requests. This differs from the case with test coverage reports, where pull requests are supported. If wildcards are not noted for a given property, then they are not supported for that property. The remarks for properties that support wildcards will mention this fact. Some properties support the following wildcards in paths. Unless otherwise specified, these properties require values that are relative to the project root. The data is then displayed in your SonarQube analysis.īelow, you will find language- and tool-specific analysis parameters for importing test execution reports.įor information on analysis parameters in general, see analysis parameters. Much like tests coverage reports, test execution reports must be generated by an external tool and then imported into SonarQube by specifying a parameter telling the scanner where to look for the report. Test execution reports are not generated by SonarQube itself. This differs from test coverage reports, which describe the percentage of your code that has been tested by your test suite during a build. Test execution reports describe which tests within your test suite have been run during a build.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |