As a QA personal you will come across the word ‘Bug’ in your
day to day life or even many times a day. As a QA engineer, the primary job is
to detect these Bugs/failures/errors or unexpected result in feature/software
and deliver a quality product.
Let’s brush up the basics first before going further.
- Severity defines “How bad the defect impacts the product functionality”
- Priority defines “How soon it is desired to fix the problem”
It is very important to tag bugs with
appropriate Severity and Priority while filing the C.R(Change Request), so let us
see the what all types will come under available priority and severity list
Bug Severity:
·
0-Blocker:
A showstopper which has no work around, hang, system crash and something that
is absolutely blocking to move forward with testing
·
1-Critical:
Crash or data loss with a work-around, and critical for shipping. However, we
can keep continue with our work/testing.
·
2-Major:
Buggy feature, and something that has to be fixed, but doesn't crash, major
usability problems
·
3-Average:
Error occurs at boundary conditions, Product inconsistency, Minor feature
broken with a workaround
·
4-Minor:
Typos, Annoyances, minor usability problems
Bug Priority:
1-Highest: A show stopper, QA is blocked with testing
and must be addressed with high priority
2-High: Issue is highly desirable for the release under development
3-Medium: Issue is desirable for the release under development
4- Low: Issue is of very low importance for the release or features under development
2-High: Issue is highly desirable for the release under development
3-Medium: Issue is desirable for the release under development
4- Low: Issue is of very low importance for the release or features under development
It is very important to specify all the details of the bug.
A short and nice headline, an informative description, steps to reproduce and
related log files, screenshot and projects, etc.
QA job doesn’t end after filing a bug, we have to keep track
of the things that what bugs are fixing in the release and what are closed as
not reproducible/not valid. An eye should be kept on postponed bugs as well.
Not only these, bugs triaging is also one of the key factor to deliver a
quality product
Last but not the least, be careful to add all the required artifacts
while logging the bugs. Happy Testing :)
