What is the lifecycle / process of a bug? Speaking generally, Are there any tips, suggestion process wise that bug fixing should go though?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What is the lifecycle / process of a bug? Speaking generally, Are there any tips, suggestion process wise that bug fixing should go though?
A few things beyond the standard Find->Fix->Test-Release cycle:
A bug should have multiple assignments, so it can be assigned to one person for fixing, and another person for testing it, instead of being assigned to a single person.
Your bug track system must track all history of what was changed.
Keep track of what version a bug was found in, was fixed in, was tested in, and then was released in. They are all different and important values.
Have the ability to change an issue from a bug to an enhancement.
Have a status for “question” or “waiting for answers”, to represent questions have been sent to a business analyst, essentially blocking progress on the bug.
Keep a bug restricted to a single issue, so that you can verify whether that issue is acutally fixed. So if there are 3 things wrong with a screen, log 3 bugs, instead a single of “Issues on the Whatever Screen”; these bugs may be fixed and released individually, and you need to be able to track that.