A defect process, a process where project related defects (bugs) are addressed and resolved, can be run efficient or can become frustrating and very time consuming. Certain people don't take up their responsibilities, certain procedures are not clear and therefore not followed. Defects start flying up and down between parties and start revealing some people's deepest emotional frustrations or interesting dialogues, sometimes they even carry the only analysis of a certain topic available in the whole program...
A defect is not an information exchange process, nor is it an analysis addendum or personal ventilation tool. A defect should be clear and unambiguous. The turn-around time of a defect should be quick. Therefore a defect needs to be light and to the point.
ProcessThe defect status flow is most often discussed. You might be using the companies existing process flow. However, often even if the process is defined, it is not always unambiguously explained. When your company is less mature in testing and test process implementation, it is advised to keep status flows as simple as possible. More statuses require more overhead and result in more confusion.
The 3 main questions you need to clarify in order to describe a defect process are:
- What are the circumstances for a defect to arrive in a certain status?
- Which role is responsible to treat a defect when it arrives in a certain status?
- What are the next possible statuses a defect can arrive in?
Defect proceduresDefect procedures look into your particular instance of the maybe generic defect flow. Who will take up certain roles? What are the steps to be undertaken in certain situations? Agree on clear responsibilities.
These are, which I found vital defect procedures
- Defect coordination board with as main purpose treating defects that are not agreed upon.
- Defect retest procedures. Who retests where and how do we know a defect fix is deployed in which environment.
Defect guidelines or instructions
Defect guidelines or instructions are the good practices you share with all testers and developers when registering a defect. A developer needs to know how to reproduce a defect and a manager needs to see what a defect is exactly about at a first glance.
These are defect guidelines that I find most important:
- Summary - One line issue description, following a convention of giving the location where the defect occurred and a short and clear description of the defect that occurs: e.g. Billing - Field 'Street' should also accept numeric values
- Comments - Comments are added to a defect after them being discussed. No changes are made to a defect without a complete and concise explanation.
- Prioritization - Define severity, impact and priority parameters unambiguously. The more statuses you invent, the more complex it will become to keep an overview. Keep it simple.