Bug tracking
Bug tracking is a process in
which the defects are identified, Isolated and managed
Defect
Profile Template:
Defect –ID: -
The lists of defect numbers are
mentioned here in this section.
Defect
Description: -
What exactly the defect is
clearly described here in this section.
Steps
for reproducibility: -
The list of all the steps that
are followed by the test engineer to identify the defect will be listed out
here in this section.
Submitter:
-
The name of the test engineer who
has submitted the defect will be mentioned here in this section.
Date
Submission: -
The date on which the defect is
submitted is mentioned here in this section.
Version
No: -
Corresponding Version number is
mentioned here in this section.
Build
No: -
Corresponding build number is
mentioned here in this section.
Assigned
To: -
The development lead will fill
the developer’s name for which the defect is assigned.
Severity: -
How serious the defect is
defined in terms of severity, Severity is classified in to four types:
1. Fatal (Sev1) or S1 or 1
2. Major (Sev2) or S2 or 2
3. Minor (Sev3) or S3 or 3
4. Suggestion (Sev4) or S4 or 4
1.
Fatal:
|
|
|
|
If at all the problems are related to the navigational blocks or
unavailability of functionality then such type of defects is treated to be
fatal defect.
 |
|||
 |
|||
2. Major: -
If at all the problems are related to the
working of major functionalities then such types of defects are treated to be
major defects.
|
|
|
|
 |
3. Minor:-
If at all the problems are related to the Look & Feel of the application then such type of defects are treated to be minor defects
 |
4. Suggestions: -
If
at all the problems are related to the value of the application then such type
defects are treated to be suggestions.
 |
+Ve integer Box Priority: -
Priority
defines the sequence in which the sequence in which defects has to be
rectified. It is classified in to four types
1. Critical (Pri1) or P1 or 1
2. High (Pri2) or P2 or 2
3. Medium (Pri3) or P3 or 3
4. Low (Pri4) or P4 or 4
Usually the Fatal defects are given critical priority, Major defects are
given High priority, Minor defects are given Medium Priority and suggestions
are given Low Priority, But depending up on the situations the priority will be
changing.
I
- Case:
Low
severity-High Priority Case: -
Up
on customer visit to the company all the look and feel defects are given
highest priority.
II
- Case:
High
severity –Low Priority Case: -
Whenever
80% of the application is released to testing department as 20% is missing the
test engineers will treat them as Fatal defect but the development lead will
give least priority for those defects as features are under development.
Bug Life Cycle: -
Defect life cycle is a cycle which a defect goes through during its lifetime
 |
|||||||||||||||||
 |
|||||||||||||||||
 |
|||||||||||||||||
 |
|||||||||||||||||
 |
|||||||||||||||||
|
|||||||||||||||||
 |
|||||||||||||||||
 |
|||||||||||||||||
 |
|||||||||||||||||
 |
No
Build
#1
 |
Build
#2
 |
|||
 |
|||
Yes
No
 |
Yes |
|||
 |
|||
No
Status: -
New: -
Whenever the defect is found for the
first time the test engineer will set the status as New.
Open: -
Whenever the developer accepts the raised
defect then he will set the status as open.
Fixed for verification Or Fixed for
rectified: -
Whenever the developer rectifies the
raised defect then he will change the status to fix.
Re open and Closed: -
Whenever the defects are rectified, next
build is released to the testing dept then the test engineers will check
whether the defects are rectified properly or not. If the defect is rectified
properly then the test engineer will set the status as “Closed”. If the defect
is not rectified properly then the test engineer will set the status as “Re
open”.
Hold: -
Whenever the developer is confused to
accept or reject the defect then he will set the status of the defect as hold.
Testers Error or Testers Mistake Or
Rejected: -
Whenever the developer is confirmed it
is not at all a defect hen he will set the status of the defect as “Rejected”.
As Per Design: -
When ever the test engineer is not
aware of new requirements and if he raises defects related to the new features
then the developer will set the status “
As Per Design”.
Note: This is a rare case not usually Occurs
Error: When we get the wrong output i.e. syntax error, logical error
Fault: When everything is correct but we are not able to get a result
Failure: We are not able to insert any input
Defect: if it is
not working as for the customer expectations
No comments:
Post a Comment