Answer Posted / lakshmanaraj bg

Life Cycle of a Bug:

Given below are the stages of a bug life span. Test reports describe in detail the behavior of bug at each stage.

New:

This is the first stage of bug life cycle in which the tester reports a bug.

The presence of the bug becomes evident when the tester tries to run the newly developed application and it does not respond in an expected manner.

This bug is then send to the testing lead for approval.

Open:

When the bug is reported to the testing lead, he examines the bug by retesting the product.

If he finds that the bug is genuine, he approves it and changes its status to 'open'.

Assign:

Once the bug has been approved and found genuine by the testing lead, it is then send to the concerned software development team for its resolution.

It can be assigned to the team who created the software or it may be assigned to some specialized team.

After assigning the bug to the software team, the status of the bug is changed to 'assign'.

Test:

The team to which the bug has been assigned works on the removal of bug.

Once, they are finished with fixing the bug, it is sent back to the testing team for a retest.

However, before sending the bug back to the testing team, its status is changed to 'test' in the report.

Deferred:

If the development team changes the status of the bug to 'deferred', it means that the bug will be fixed in the next releases of the software.

There can be myriad reason why the software team may not consider fixing the bug urgently.

This includes lack of time, low impact of the bug or negligible potential of the bug to induce major changes in the normal functioning of the software.

Rejected:
Although, the testing lead might have approved the bug stating it as a genuine one, the software development team may not always agree.

Ultimately, it is the prerogative of the development team to decide if the bug is really genuine or not.

If they doubt the presence or impact of the bug, then they may change its status to 'rejected'.

Duplicate:

If the development team finds that the same bug has been repeated twice or there are two bugs which point to the same concept, then the status of one bug is changed to 'duplicate'.

In this case, fixing one bug automatically takes care of the other bug.

Verified:

If the software development team sends the fixed bug back for retesting, then the bug undergoes rigorous testing procedure again.

If at the end of the test, it is not found then its status is changed to 'verified.'

Reopened:

If the bug still exists, then its status is changed to 'reopened'.

The bug then traverses the entire of its life cycle once again.

Artifacts in design phase of SDLC ?

3522

---

Hi, Anybody knows about Hexaware company..

2093

---

What is decision table testing?

1111

---

how to test the case with 5 combination and inputs

2052

---

hi this is ashok , i never worked in medical domain , can any one pls send me with proper exaple pls Question is while emergency or normal patitent enter into hospital he entered his first and last name and he enter emergency coloumn , write test case on these ,

2046

---

What is mean by multi-threading testing?

2649

---

I studied MBA, I want learn any softwarecourse, which course is better hadoop or testing tools(manual+selenium?)

1647

---

What is a defect?

1164

---

what technical problem u face in your module please tell what is it mean its any bug or anything else i want ans give any example which ever modul u r working for u can give me any example

2308

---

What is test driver and test stub?

1158

---

What are the different ways of doing black box testing?

1072

---

WHAT IS PROTOCAL TESTING..EXPLAIN? L2, L3 PROTOCALS TESTING MEANS WHAT?EXPLAIN BRIEFLY

6779

---

how deployment phase of SDLC differs in product based and in service based company ?

2962

---

HI GUYS,, I HAVE 3 YEARS OF EXP IN MANUAL TESTING...NEXT MONTH ONWARDS I WORK FOR MOBILE TESTING....PLS SUGGEST ME WHAT I LEARN FOR TRAING,, MOBILE TESTING OR ANDROID....FOR MOBILE TESTERS NEED ANDROID(IFONE) DEVOLOPMENT KNOWLEDGE OR NOT? EXPLAIN CLEARLY

2133

---

why testcases are written and what is the importance?

1593

---