Critical Issues
A Critical issue shouldn't move to production (it can for business imperatives) but must be fixed during the next iterations.
Severity is defined in the rule source code or inferred from the issue annual interest and thresholds in Project Properties > Issue and Debt.
Severity is defined in the rule source code or inferred from the issue annual interest and thresholds in Project Properties > Issue and Debt.
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 Issues" Unit="issues" />
failif count > 10 issues
warnif count > 0 issues
from i in Issues
where i.Severity == Severity.Critical
select new { i, i.Severity, i.Debt, i.AnnualInterest }
//<Desc>
// A **Critical** issue shouldn't move to production (it can for business
// imperatives) but must be fixed during the next iterations.
//
// Severity is defined in the rule source code or inferred from the issue
// *annual interest* and thresholds in Project Properties > Issue and Debt.
//</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