testPaths is not relative to basePath, unlike outputFile #30
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is one possible way to add test file paths relative to
basePath
, to make it consistent and not break backwards compatibility oftestPaths
andtestFilePattern
. Note that I'm not a fan of my new config item name (basePathGlob
) but having trouble thinking of a better one. "testFilesGlobFromBasePath" is a bit cumbersome. Naming is hard.The gist is that config item
sonarQubeUnitReporter.basePathGlob
is a globbed file path, relative tobasePath
, that will overridetestPaths
andtestFilePattern
. The path attribute that ends up in the outputFile xml is also relative tobasePath
.Cheers!