What do you do when you find a bug?
Hold on do not answer it right now. Let me first set the context.
You are part of an agile team. The developers sit opposite to you. You are testing a feature in a session. You are time bound and have the good habit of capturing notes when you test. When you now find a bug what do you do? Assuming that you have taken enough notes you go on to write a good bug description and may capture a screen shot, video of the bug and continue with your session. At the end of the session do you
Open the defect tracking tool (wait for it to load), enter all the fields for a bug, upload necessary evidence and have the tool share the defects with your dev team?
Open the defect tracking tool (wait for it to load), enter all fields for a bug, upload necessary evidence and then compose an email to the dev team with the bug idís/descriptions?
Walk to the developer share your notes; reproduce it if required, work together to identify the problem?
I work in an agile team; we collaborate together with the dev team to deliver our stories and in turn the product. When we find a bug we walk up to the developer, share our test notes and bugs with them. If the developer have more questions we work together for may be 30 min to try identify the root cause together. We then attach the session sheet to the task in mingle (project tracking tool) and update our coverage sheet. If we identify a bug as ďout of sprintĒ we log it in mingle.
I have seen that this process is much quicker. It takes approx 1 min to ask if the developer is free for an update and the next 10 min to update the session notes and bugs.
Apart from a quick feedback, this process has also helped in bridging good communication between testers and dev team. Dev team are amazed by the scenarios, test notes captured during testing and this has lead to admiration of the test team. Testers understand and learn more about the system every time they pair up with the dev team to discuss test notes.
This process has made me wonder if itís time we need newer, lighter, interactive defect tracking tools? Or do we need it all? I might write a series about this.
... to read more articles, visit http://sqa.fyicenter.com/art/