DEFECT LIFE CYCLE / BUG LIFE CYCLE

DLC consists of below mentioned status

1. New/open
2. Assigned
3. Fixed
4. Closed
5. Re-open
6. Reject
7. Defect cannot be fixed
8. postponed
9. duplicate
10. issue not reproducible
11. RFE (request for enhancement)

ISTQB question

What is the difference b/w NEW and OPEN status?

For the first time when TE finds the defect status will be new
When developer starts to work on the defect then the status will be open

What is reject status?

1. TE will find a defect and send it to DE now dev says it is not a defect it is a feature, in this case dev
will change the status as reject status

2. Because of referring old requirement

3. Because of adding extra features:

Whenever test engineer finds an extra feature, which is not in the requirement TE will raise it as defect,
in this case sometimes dev will say it is not a defect because the feature is working now test engineer
should reopen the defect and ask dev to update the requirement.

4. When the build / software is wrongly installed or wrongly configured :

If TE install build wrongly and find defect in the software and communicate to developer now
developer will tell it is not a defect because code is perfect but TE has not installed the build properly

What is Duplicate status?

TE finds the defect and communicate to dev if the same defect is already tracked by some other T.E.
Why we get duplicate status?

1.Because of testing common feature

2.Assume that old TE is working on project and he has found 100 defects, 60 defects are fixed by the
developers and 40 are not fixed, TE quits the job, new TE joins the same project and fins same 40 defects
and they are duplicates of old defects

Interview question

Q. Why developer says it is duplicate?

1. To reduce defect count
2. To reduce duplicate effort

Q. How to avoid duplicate defects?

1. TE when they find defects and communicate to DL keep CC to TL and also to TE who are working on
same project and present in your team
2. Before we prepare report and log the bug we should search for duplicate bugs in the tool by using
certain keywords (in this case sales_blank page)

3.TE when we find defect before we track, we should cross check with senior TE, TL and dev sometimes
so that we can avoid duplicates
Q. What is defect cannot be fixed status?
1. If TE finds a defect in the root of the product and it’s a minor defect and if it is not affecting the
customer business work flow then dev will tell defect cannot be fixed

2.If the cost of fixing the defect is more than the cost of defect then dev says that defect cannot be fixed
(cost of defect- loss in business because of having defect in software)

Q. What is postponed status?

Here developers are accepting that it is a defect but they want to fix it little late, in such a case they say
that fix the defect in future release or change the status as postpone

Q Why we get postponed status?

1. If TE finds minor defect in the end of the release, if dev is not having sufficient time to fix the defects
then dev will tell he will fix the defect in future release
2. If TE finds a defect in a feature which is not required to the customer in the current release then dev
will tell he will fix the defect in future release
 3. If TE finds a defect in feature where customer wants to do lot of changes in req, on same features and
even customer might remove the feature as well, in this case dev will tell he will fix the defect in future
release/postpone the defect
4. If TE finds a defect in a feature which is exposed to internal users and if it is a minor defect then dev
will tell he will fix the defect in future release

Q. What is issue not reproducible status?

TE is able to see the defect but dev is not able to see the same defect then it is called issue not
reproducible status

Q. Why we get reproducible status?

1. Because of platform mismatch
* Because of OS mismatch
* Because of browser mismatch
* Because of browser version mismatch
* Because of browser setting mismatch
4. Because of inconsistent defect
What is inconsistent defect? or ghost defect?
If a feature is not working for some time and same feature is working for some other time OR
sometime defect appears and sometimes defect disappears this is called as inconsistent defect If TE
finds this kind of defect then he should track the defect in DDT and write a note stating that defect is
inconsistent
Q. what is RFE/CR? (request for enhancement or change request)
While testing the s/w if TE finds defect in the s/w which is not a part of the requirement then it is
called as RFE/CR