From 4466f744cfb669a2ad6d9af94c321d16ff26cee1 Mon Sep 17 00:00:00 2001 From: Peeter Piegaze <61758048+peeter-piegaze-sonarsource@users.noreply.github.com> Date: Fri, 15 Jul 2022 18:56:36 +0200 Subject: DOC-20 Temporarily adjust URL of coverage page in SQ docs (#6300) --- server/sonar-docs/src/pages/analysis/analysis-parameters.md | 2 +- server/sonar-docs/src/pages/analysis/test-coverage/overview.md | 2 +- .../src/pages/analysis/test-coverage/test-execution-parameters.md | 2 +- .../sonar-docs/src/pages/project-administration/narrowing-the-focus.md | 2 +- server/sonar-docs/static/SonarQubeNavigationTree.json | 2 +- server/sonar-docs/static/StaticNavigationTree.json | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/server/sonar-docs/src/pages/analysis/analysis-parameters.md b/server/sonar-docs/src/pages/analysis/analysis-parameters.md index a88ba5da6dd..785904ee35c 100644 --- a/server/sonar-docs/src/pages/analysis/analysis-parameters.md +++ b/server/sonar-docs/src/pages/analysis/analysis-parameters.md @@ -15,7 +15,7 @@ For example, if you override the `sonar.exclusions` parameter via command line f Most of the property keys shown in the interface at both global and project levels can also be set as analysis parameters, but the parameters listed below can _only_ be set at analysis time. -For language-specific parameters related to test coverage and execution, see [Test Coverage](/analysis/test-coverage/overview/). +For language-specific parameters related to test coverage and execution, see [Test Coverage](/analysis/coverage/). For language-specific parameters related to external issue reports, see [External Issues](/analysis/external-issues/). [[info]] diff --git a/server/sonar-docs/src/pages/analysis/test-coverage/overview.md b/server/sonar-docs/src/pages/analysis/test-coverage/overview.md index a6f5eb61ea5..b1b14504384 100644 --- a/server/sonar-docs/src/pages/analysis/test-coverage/overview.md +++ b/server/sonar-docs/src/pages/analysis/test-coverage/overview.md @@ -1,6 +1,6 @@ --- title: Overview -url: /analysis/test-coverage/overview/ +url: /analysis/coverage/ --- Test coverage reports and test execution reports are important metrics in assessing the quality of your code. diff --git a/server/sonar-docs/src/pages/analysis/test-coverage/test-execution-parameters.md b/server/sonar-docs/src/pages/analysis/test-coverage/test-execution-parameters.md index c362b4e3572..1535a8ebe37 100644 --- a/server/sonar-docs/src/pages/analysis/test-coverage/test-execution-parameters.md +++ b/server/sonar-docs/src/pages/analysis/test-coverage/test-execution-parameters.md @@ -6,7 +6,7 @@ url: /analysis/test-coverage/test-execution-parameters/ _Test execution reports_ describe which tests within your test suite have been run during a build. This differs from _test coverage reports_, which describe the percentage of your code that has been tested by your test suite during a build. -For details, see [Test Coverage](/analysis/test-coverage/overview/). +For details, see [Test Coverage](/analysis/coverage/). Test execution reports are not generated by SonarQube itself. 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. diff --git a/server/sonar-docs/src/pages/project-administration/narrowing-the-focus.md b/server/sonar-docs/src/pages/project-administration/narrowing-the-focus.md index b04179cae92..ea8b8650cbc 100644 --- a/server/sonar-docs/src/pages/project-administration/narrowing-the-focus.md +++ b/server/sonar-docs/src/pages/project-administration/narrowing-the-focus.md @@ -221,7 +221,7 @@ Note that the initial scoping parameter for test code is `sonar.tests` (that's ` ### Relation to test coverage reporting -The test scoping parameters ( `source.tests`, `sonar.test.exclusion`, and `sonar.test.inclusion`) do not have anything to do with setting up test coverage reporting (see [Test Coverage](https://docs.sonarqube.org/analysis/test-coverage/overview/)). However, SonarQube will report an error if an imported coverage report lists a test file not encountered in the directories specified by the scoping parameters. +The test scoping parameters ( `source.tests`, `sonar.test.exclusion`, and `sonar.test.inclusion`) do not have anything to do with setting up test coverage reporting (see [Test Coverage](/analysis/coverage/)). However, SonarQube will report an error if an imported coverage report lists a test file not encountered in the directories specified by the scoping parameters. The parameter `sonar.coverage.exclusions`, on the other hand, is directly related to test coverage reporting (see below). diff --git a/server/sonar-docs/static/SonarQubeNavigationTree.json b/server/sonar-docs/static/SonarQubeNavigationTree.json index ba5ad9e45fc..40a0d83af80 100644 --- a/server/sonar-docs/static/SonarQubeNavigationTree.json +++ b/server/sonar-docs/static/SonarQubeNavigationTree.json @@ -53,7 +53,7 @@ { "title": "Test Coverage", "children": [ - "/analysis/test-coverage/overview/", + "/analysis/coverage/", "/analysis/test-coverage/java-test-coverage/", "/analysis/test-coverage/javascript-typescript-test-coverage/", "/analysis/test-coverage/dotnet-test-coverage/", diff --git a/server/sonar-docs/static/StaticNavigationTree.json b/server/sonar-docs/static/StaticNavigationTree.json index 9066f5bda2d..2b897862952 100644 --- a/server/sonar-docs/static/StaticNavigationTree.json +++ b/server/sonar-docs/static/StaticNavigationTree.json @@ -78,7 +78,7 @@ { "title": "Test Coverage", "children": [ - "/analysis/test-coverage/overview/", + "/analysis/coverage/", "/analysis/test-coverage/java-test-coverage/", "/analysis/test-coverage/javascript-typescript-test-coverage/", "/analysis/test-coverage/dotnet-test-coverage/", -- cgit v1.2.3