Results 1 to 2 of 2

Thread: Changing staus of defect

  1. #1
    Moderator
    Join Date
    Oct 2005
    Answers
    305

    Changing staus of defect

    Can developers change staus of defect? How to configure this? what needs be done.

    Thanks

    NOTE : [This question was asked by Ivn]


  2. #2
    Banned
    Join Date
    Dec 2006
    Answers
    4

    Re: Changing staus of defect

    Hi , the duration or time span between the first time bug is found (`new') and closed successfully (status: `closed'), rejected, postponed or deferred is called as `bug/error life cycle'. (right from the first time any bug is detected till the point when the bug is fixed and closed, it is assigned various statuses which are new, open, postpone, pending retest, retest, pending reject, reject, deferred, and closed. For more information about various statuses used for a bug during a bug life cycle, you can refer to article `software testing bug & statuses used during a bug life cycle') there are seven different life cycles that a bug can passes through: < i > cycle i: 1) a tester finds a bug and reports it to test lead. 2) the test lead verifies if the bug is valid or not. 3) test lead finds that the bug is not valid and the bug is `rejected'. < ii > cycle ii: 1) a tester finds a bug and reports it to test lead. 2) the test lead verifies if the bug is valid or not. 3) the bug is verified and reported to development team with status as `new'. 4) the development leader and team verify if it is a valid bug. The bug is invalid and is marked with a status of `pending reject' before passing it back to the testing team. 5) after getting a satisfactory reply from the development side, the test leader marks the bug as `rejected'. < iii > cycle iii: 1) a tester finds a bug and reports it to test lead. 2) the test lead verifies if the bug is valid or not. 3) the bug is verified and reported to development team with status as `new'. 4) the development leader and team verify if it is a valid bug. The bug is valid and the development leader assigns a developer to it marking the status as `assigned'. 5) the developer solves the problem and marks the bug as `fixed' and passes it back to the development leader. 6) the development leader changes the status of the bug to `pending retest' and passes on to the testing team for retest. 7) the test leader changes the status of the bug to `retest' and passes it to a tester for retest. 8) the tester retests the bug and it is working fine, so the tester closes the bug and marks it as `closed'. < iv > cycle iv: 1) a tester finds a bug and reports it to test lead. 2) the test lead verifies if the bug is valid or not. 3) the bug is verified and reported to development team with status as `new'. 4) the development leader and team verify if it is a valid bug. The bug is valid and the development leader assigns a developer to it marking the status as `assigned'. 5) the developer solves the problem and marks the bug as `fixed' and passes it back to the development leader. 6) the development leader changes the status of the bug to `pending retest' and passes on to the testing team for retest. 7) the test leader changes the status of the bug to `retest' and passes it to a tester for retest. 8) the tester retests the bug and the same problem persists, so the tester after confirmation from test leader reopens the bug and marks it with `reopen' status. And the bug is passed back to the development team for fixing. < v > cycle v: 1) a tester finds a bug and reports it to test lead. 2) the test lead verifies if the bug is valid or not. 3) the bug is verified and reported to development team with status as `new'. 4) the developer tries to verify if the bug is valid but fails in replicate the same scenario as was at the time of testing, but fails in that and asks for help from testing team. 5) the tester also fails to re-generate the scenario in which the bug was found. And developer rejects the bug marking it `rejected'. < vi > cycle vi: 1) after confirmation that the data is unavailable or certain functionality is unavailable, the solution and retest of the bug is postponed for indefinite time and it is marked as `postponed'. < vii > cycle vii: 1) if the bug does not stand importance and can be/needed to be postponed, then it is given a status as `deferred'. This way, any bug that is found ends up with a status of closed, rejected, deferred or postponed. Regards, sydhu


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
About us
Applying for a job can be a stressful and frustrating experience, especially for someone who has never done it before. Considering that you are competing for the position with a at least a dozen other applicants, it is imperative that you thoroughly prepare for the job interview, in order to stand a good chance of getting hired. That's where GeekInterview can help.
Interact