Bug Bug can be defined as the abnormal behavior, error, defect in a software.

The detection of bugs depends on the efficiency of the testing done. Bug or Defect life Cycle Basic bug cycle is explained in the picture below.

New : When the bug is posted for the first time, its state will be NEW means that the bug is not yet approved. Open: After a tester has posted a bug, the test lead approves that the bug is genuine and he changes the state as OPEN. Assigned : Once the lead changes the state as OPEN, he assigns the bug to corresponding developer or development team and state of bug is changed to ASSIGN. Test : Once the developer fixes the bug, he has to assign the bug to the testing tam for next round of testing. Before he releases the software with bug fixed, he changes the state to TEST. It means that bug has been fixed and is released to testing team. Deferred/ Postpone : The bug changed to DEFERRED state means the bug is expected to be fixed in next releases. There may be many factors for changing the bug to this state like priority of the bug may be low, lack of time for the release or the bug may not have major effect on the software. Postpone means will be fixed later and not decided when it will be fixed.

1. 2. 3. 4. 5. 6.

Rejected : If the developer feels that the bug is not genuine, he rejects the bug. Then the state of the bug is changed to REJECTED. Duplicate: If the bug is already reported or other bug defines the same issue, then one bug status is changed to DUPLICATE. Verified : Once the bug is fixed and the status is changed to TEST, the tested tests the bug. If the bug is not present in the software, he approves that the bug is fixed and changes the status to VERIFIED. Reopened : If the bug still exists even after the bug is fixed by the developer, the tester changes the status to REOPENED. The bug traverses the life cycle once again. Closed : Once the bug is fixed, it is tested by the tester. If the tester feels that the bug no longer exists in the software, he changes the status of the bug to CLOSED. This state means that the bug is fixed, tested and approved. Contents of a Bug Report Defect ID : unique number/reference given to each bug Program/module being tested : the name of the program/module that is being tested or issue found Version and release number : the version of the software in which issue is found Problem Summary : Short precise one liner Priority High -> Cannot proceed further blocked Medium ->Manageable less impact low -> Nice to have Report Type : describes the type of the problem Severity : how sever is the issueu view the bug. Levels of severity : High/Critical -> Core functionality does not work/ threat to life and system Medium -> Basic function does not work /Manageable low -> Nice to have Environment : in which environment bug was found Detailed description : How to reproduce : detailed description of how to reproduce the bug Reported by : the name of the person who writes the report Assigned to developer : name of the developer who assigned to fix the bug Status : Open : the status of bug when it entered Fixed / feedback : the status of the bug when it fixed Closed : The status of the bug when verified Deferred : the status of the bug when it postponed User error : the status of the bug when user made an error Not a bug : the status of the bug when it is not a bug 13.Priority : assigned by the project manager who asks the programmers to fix bugs in priority order. 14. Resolution : Defines the current status of the problem (5 types- integrated, deferred, not a problem, will not fix, as designed)

o o o
7. 8. 1.

1. 2. 3. 4. 5. 6.