While looking analysis results, you could find that (for example) a Kiuwan rule is generally helpful and must be kept active. But, in some concrete cases, it is not applicable (or it is not properly working) and some defects should not be considered in the analysis.
Reasons to “silence” (or mute) those defects can be of very different nature but you might decide that, the rule should not be applied in certain particular cases o situations.
In any case, you want to keep active the rule but discard some specific defects. Kiuwan provides the Mute Defect functionality to do it.
Please, also have a look at How to manage Kiuwan defects when I do not completely agree with them
Defects muting can be applied to three different scopes:
Kiuwan allows you to declare mute patterns for all the above situations, letting you to suite Kiuwan muting mechanism to your specific needs.
What is important to remember is that muted defects will not be considered when passing an Audit or calculating any Indicator.
Muted defects are still there (you can inspect them) but will not be part of the calculations made by Kiuwan.
Probably, you might be wondering at this moment some questions:
Kiuwan allows you to mute defects at any moment of your applications life cycle.
If you are using Kiuwan Life Cycle, most probably you will have application baselines (performed periodically at quite defined promotion to production stages) and deliveries (at nightly-build or quite often while continuous development).
In previous releases, Kiuwan only allowed you to mute defects in baseline analyses. Now, you can also mute defects found during a delivery analysis.
In summary, you can mute defects at any moment of your application life cycle.
After an analysis, you will need to spend some time looking carefully to the defects found during the analysis, to fully understand them before to consider submit its correction to developers. During that review, some of them will be reviewed very fast but other may take a while.
Kiuwan can help you to mark the “Review Status” for any specific defect.
This way, as you review the defects you can mark them as “To review” or “Reviewed” (or leaving blank, of course) for review tracking purposes.