Defect Severity
Last updated
Was this helpful?
Last updated
Was this helpful?
We use this to ... so that we can ...
Defect Severity is defined as the degree of impact a defecthas on the software application under test. A higher effect of the defect on system functionality will lead to a higher severity level.
The Test Analyst will initially determine the Severity level of the defect based on a combination of their own system knowledge and impact on their testing.
However, this determination should be supported by conversations with the Devs, BAs, Business SMEs or Product Owner to understand the potential business impacts correctly.
A defect that causes critical disruptions to the business operation and no workarounds are available. A defect that causes the application or a critical function to crash or produce incorrect results. A defect that would cause critical data, compliance, or regulatory breaches. Blocks all testing efforts and has no way to proceed.
A major defect would result in the loss of some business functionality and would require an unacceptable workaround in Production. A defect that makes a major functionality/feature behave grossly differently from what is expected or specified in the requirements. A defect that would cause negative Brand impacts. (To be determined by PO, Business Owner) Blocks testing efforts for an area in scope for this sprint
A Moderate defect is one that occurs when the product or application doesn't meet certain criteria or produces an undesirable behaviour. However, the functionality as a whole is not impacted.
Defects where an acceptable workaround is available.
A Minor severity defect including anything cosmetics such as spelling mistakes, incorrect alignment, and font displays. This defect is also for any issues that do not affect functionality or data.
No workarounds are required.