What does the classification of error severity depend on?

The classification of severity level of defects primarily depends on the degree of impact of the defect on the system's operability, functionality, and user interaction.

Main factors determining severity:

• Impact on key functionality: How much the defect hinders the execution of core functions for which the product was created.
• Level of impact on the user: Whether the defect makes the product unusable, inconvenient, or simply causes minor irritation.
• Workaround possibility: Is there a way to bypass the defect and continue working, or does it completely block task execution.
• Frequency of occurrence: How often the user encounters this defect.
• Risk of data loss: Can the defect lead to loss or damage of user data.
• Impact on security: Does the defect pose a threat to data or system security.
• Compliance with requirements: How much the defect violates specified requirements.

Standard severity levels (may vary depending on the project):

• Blocker: Critical error that makes it impossible to use key functionality or blocks further testing. Requires immediate fixing.
• Critical: Serious error affecting main functionality but may have a workaround. Significantly worsens user experience.
• Major: Significant error affecting secondary functionality or causing serious inconvenience but does not make the product completely unusable.
• Minor: Insignificant error related to visual display, usability, or secondary functionality, not affecting core operation.
• Trivial/Cosmetic: Minor error that does not affect functionality or usability (e.g., typos).

It is important to have clear criteria for each severity level, agreed upon with the team and stakeholders, to ensure consistency in defect assessment.