Severity (S) is the indication of bug’s effect and impact on the customers. For any new bug, this is the first thing to be determined while filing the bug.
Typically, severity is divided into five levels and are: S1 (Highest), S2, S3, S4, S5 (Lowest)
- S1: means that the feature can’t be tested or blocking further testing
- S2: majority features are not working, and many tests are failing
- S3: some cases are not working
- S4, S5: very corner cases and not impacting the major functionality
The bug filer would determine the severity and set while filing the bug.
No. Typically, once set the severity in the bug, then no changes can be done. Typically, bug tools will not allow changing the severity.
Like this:
Like Loading...
Author: Jagadesh Babu Munta
Jagadesh Babu Munta is working as a Consulting Member of Technical Staff with Oracle America Inc. He has been with Oracle and Sun Microsystems together for over 16 years (since June 2000) in USA. Jagadesh has overall 20+ years of Software development and quality/testing experience. Jagadesh's experience has been filled recently with Cloud PaaS services, Multi-Tenancy, Security and Penetration testing. In the past, he extensively worked on Java EE servers like SailFin/GlassFish/Sun Java System/iPlanet/Netscape Application Servers. Jagadesh has gained extensive expertise in software automation, designing frameworks, writing tools, scripts, creating tests, writing specs/plans, etc. Jagadesh is interested in developing and testing complex software useful to up-level the humanity. Jagadesh Munta holds M.S. in Software Engineering from San Jose State University, California, USA; B.Tech. in Computer Science and Engineering from J.N.T.U., Hyderabad, India; Special Diploma in Electronics with Specialization in Computer Engineering, G.I.O.E, Secunderabad, India. Jagadesh Munta was born in Nellore, AP., India and lives with family in Fremont, California, USA.
View all posts by Jagadesh Babu Munta
Software Quality and Java Automation 