The UnusedSuppressionRuleAnalyzer is very useful but unfortunately its output is buried in the build output.
Ideally, we would have zero suppressions that we did not need.
Would it instead be possible to include each failed suppression in the output report, e.g. as failed testcases?
This would be opt-in, with a setting like report-unused-suppressions-as-failures.
Alternatives (such as using grep on the build output) aren't as clean, e.g. they might fail if the logged message changes.
They would also have to be implemented in each build script we have.
The proposed solution would just need enabling in the options, then would automatically be compatible with our existing usage.
A bonus feature could also be that active suppression rules (i.e. those that are not unused) could be listed as successful testcases, making it possible to see all suppressions as part of the output, regardless of whether they were unused or not.
The
UnusedSuppressionRuleAnalyzeris very useful but unfortunately its output is buried in the build output.Ideally, we would have zero suppressions that we did not need.
Would it instead be possible to include each failed suppression in the output report, e.g. as failed testcases?
This would be opt-in, with a setting like
report-unused-suppressions-as-failures.Alternatives (such as using grep on the build output) aren't as clean, e.g. they might fail if the logged message changes.
They would also have to be implemented in each build script we have.
The proposed solution would just need enabling in the options, then would automatically be compatible with our existing usage.
A bonus feature could also be that active suppression rules (i.e. those that are not unused) could be listed as successful testcases, making it possible to see all suppressions as part of the output, regardless of whether they were unused or not.