The article about Defect severity levels in software testing, which assigns to created new defect report. This article very informative and useful to beginners who’s going to start their career in the software testing.
Defect severity levels in software testing
When creating a new defect report, Technical Severity should be assigned as follows:
Any issue causing system unavailability or breakage, significant functional outage, considerable performance degradation, or severe data integrity problems. Any issue regarding corporate policy, tactical business needs, or legal requirements that requires immediate attention due to time constraints.
Data Fixes (per the decision of Level II Support/SE Analyst teams). High-impact defects that does NOT have an acceptable/sustainable workaround. Noticeable performance inefficiencies (i.e. general slowness in a particular application, backlogs of output queues)
High-impact defect with reasonable workaround. Low impact issue
Cosmetic flaws, Grammatical errors, Misspellings, typo, Incorrect error validation messages, User interface glitches, test data wrapping issue, logo mismatch issue
Following severities provides, defect severity levels in software testing
|System Application Usability||Critical system or application is not working||Major functionality is not working||Some functionality is not working but application is usable||Non-functional issues does not impact usability|
|System Outage||Application is not available||Limited but not down completely||System is working but inconsistent result||Application is available but no immediate change|
|Work Around||None||For major functionality – Exists||Effective||Easy|
|Performance||Usable system performance, application hangs||General slowness, Backlogs||Slightly degraded||Does Not Impact|
|Data Impact||Important Data loss and data loss||Minor data risk||Incorrect data||None|
|Other reasoning||Error pages, Workflow cannot be completed, third party application unavailable||Navigation problem||UI related Issues and incorrect validation error messages||Cosmetic errors, Typo errors, Grammar issues, Tab sequence, Help Issues, Missing documentation, Code not up to standard|
Soon I will provide more details about defect severity and priority with practical examples.