Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve test sensors to execute them only when the related property is defined #364

Closed
Evangelink opened this issue May 24, 2017 · 2 comments
Assignees
Labels
Area: SQ Plugin Java plugin related issues.
Milestone

Comments

@Evangelink
Copy link
Contributor

Update sensors so they are executed only when the related property is defined.

For example test sensors should be activated only when one of the following property is set (see here):
/d:sonar.cs.vstest.reportsPaths=
/d:sonar.cs.nunit.reportsPaths=
/d:sonar.cs.xunit.reportsPaths=

Same behavior for the code coverage sensor (see here):
/d:sonar.cs.vscoveragexml.reportsPaths=
/d:sonar.cs.dotcover.reportsPaths=
/d:sonar.cs.opencover.reportsPaths=
/d:sonar.cs.ncover3.reportsPaths=

@Evangelink Evangelink added Area: SQ Plugin Java plugin related issues. Type: Improvement labels May 24, 2017
@Evangelink Evangelink added this to the 5.12 milestone May 24, 2017
@Evangelink Evangelink self-assigned this Jun 7, 2017
@Evangelink
Copy link
Contributor Author

This is currently impossible to solve this ticket because it is not possible to provide a list of possible arguments to look for to be executed. We need to wait for this ticket (SONAR-8546) to be fixed first.

@Evangelink Evangelink removed this from the 6.0 milestone Jun 8, 2017
@Evangelink Evangelink added the Status: On Hold Postponed or waiting for an answer. label Jun 8, 2017
@Evangelink Evangelink removed their assignment Jun 8, 2017
@Evangelink
Copy link
Contributor Author

Feature will be available on SonarQube 6.5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: SQ Plugin Java plugin related issues.
Projects
None yet
Development

No branches or pull requests

1 participant