DOC - Generic test execution reports don't support modules

diff --git a/server/sonar-docs/src/pages/analysis/coverage.md b/server/sonar-docs/src/pages/analysis/coverage.md
index 4da433917ff138a35f49eac7c50ac05c3490668a..3123e145dfae92eecf3d93d2f759f90ee43628ca 100644 (file)
--- a/server/sonar-docs/src/pages/analysis/coverage.md
+++ b/server/sonar-docs/src/pages/analysis/coverage.md
@@ -53,7 +53,7 @@ Unless otherwise specified, these properties require values that are relative to
 
 Language|Property|Remarks
 ---|---|---
-**All**|`sonar.testExecutionReportPaths`|Comma-delimited list of paths to execution reports in the [Generic Execution Data](/analysis/generic-test/) format.
+**All**|`sonar.testExecutionReportPaths`|Comma-delimited list of paths to execution reports in the [Generic Execution Data](/analysis/generic-test/) format. The paths must be relative to the project's base directory (root module).
 C / C++ / Objective-C|`sonar.cfamily.cppunit.reportsPath`|Path to the directory holding the [CPPUnit](http://sourceforge.net/projects/cppunit/) reports. Note that while measures such as the number of tests are displayed at project level, no drilldown is available.
 C#|`sonar.cs.vstest.reportsPaths`|Paths to VSTest reports. Multiple paths may be comma-delimited, or included via wildcards. Note that while measures such as the number of tests are displayed at project level, no drilldown is available.
 C#|`sonar.cs.nunit.reportsPaths`|Paths to NUnit execution reports. Multiple paths may be comma-delimited, or included via wildcards. Note that while measures such as the number of tests are displayed at project level, no drilldown is available.

diff --git a/server/sonar-docs/src/pages/analysis/generic-test.md b/server/sonar-docs/src/pages/analysis/generic-test.md
index b57f2691b89556668f162ee9b36a2c3a43d8bfed..525c2cc5c3a549021b1b3eaf3571bd4de7e5e3bc 100644 (file)
--- a/server/sonar-docs/src/pages/analysis/generic-test.md
+++ b/server/sonar-docs/src/pages/analysis/generic-test.md
@@ -82,7 +82,7 @@ The supported format looks like this:
        
 The root node should be named `testExecutions`. Its version attribute should be set to `1`.
 
-Insert a `file` element for each test file. Its `path` attribute can be either absolute or relative to the root of the module.
+Insert a `file` element for each test file. Its `path` attribute can be either absolute or relative to the project's base directory (root module).
 
 **Note** unlike for coverage reports, the files present in the report must be test file names, not source code files covered by tests.