Bug

Work In progress...

A condition in a software product that does not meet the software requirements (as described in the requirements specification) or end user expectations (may be unspecified but reasonable). In other words, defects are coding or logic errors that cause the program to malfunction or produce incorrect / unexpected results. The different state that a bug can have are going to be define below.

· New: When a new defect is logged and posted for the first time.

· Assigned: Once the bug is validated by a tester, the bug is assigned to a developer

· Open: The developer starts analyzing and works on the defect fix

· Fixed: When a developer makes a necessary code change and verifies the change, he or she can make bug status as "Fixed."

· Pending retest: Once the defect is fixed the developer gives a particular code for retesting the code to the tester. Since the software testing remains pending from the testers end, the status assigned is "pending retest."

· Retest: Tester does the retesting of the code at this stage to check whether the defect is fixed by the developer or not and changes the status to "Re-test."

· Verified: The tester re-tests the bug after it got fixed by the developer. If there is no bug detected in the software, then the bug is fixed, the status assigned is "verified."

· Reopen: If the bug persists even after the developer has fixed the bug, the tester changes the status to "reopened". Once again, the bug goes through the life cycle.

· Closed: If the bug is no longer exists then tester assigns the status "Closed."

· Rejected: If the developer feels the defect is not a genuine defect, then it changes the defect to "rejected." Deferred: If the present bug is not of a prime priority and if it is expected to get fixed in the next release, then status "Deferred" is assigned to such bugs.