Critical Rules Violated
Fails if any critical rule is violated. Critical rules (made so via the Critical button in the rule edition control) should never be violated.
Without a baseline, rules relying on diff are not counted, which can explain an unexpected slight decrease of this count.
Without a baseline, rules relying on diff are not counted, which can explain an unexpected slight decrease of this count.
CQLinq source
This quality gate is written in CQLinq, C# LINQ over the NDepend code model. It ships with every new NDepend project: you can read it, adapt it, or use it as a starting point for your own custom rules.
// <QualityGate Name="Critical Rules Violated" Unit="rules" />
failif count > 0 rules
from r in Rules where r.IsCritical && r.IsViolated()
select new { r, issues = r.Issues() }
//<Desc>
// Fails if any critical rule is violated. Critical rules (made so via the
// *Critical button* in the rule edition control) should never be violated.
//
// Without a baseline, rules relying on diff are not counted, which can
// explain an unexpected slight decrease of this count.
//</Desc>
Open in the interactive Rules Explorer · All default rules
Quality Gates: all 19 items
- Quality Gates Evolution
- Percentage Coverage
- Percentage Coverage on New Code
- Percentage Coverage on Refactored Code
- Percentage Coverage (JustMyCode)
- Percentage Coverage on New Code (JustMyCode)
- Percentage Coverage on Refactored Code (JustMyCode)
- Blocker Issues
- Critical Issues
- New Blocker / Critical / High Issues
- Critical Rules Violated
- Treat Compiler Warnings as Error
- Percentage Debt
- Debt
- New Debt since Baseline
- Debt Rating per Namespace
- Annual Interest
- New Annual Interest since Baseline
- Unnecessary NDepend SuppressMessageAttribute Usage