Atomic Talk Title: Better Bug Reports
This talk covers how to write better bug reports to reduce miscommunication and increase the image of the tester and the entire testing team. Paul covers how to put the information needed into your bug reports from writing an effective title to describing work arounds for the bug that is being reported.
- Bug report titles that will catch the attention of the Product Owner
- How to apply the PEOPLE WORKing mnemonic to ensure your bug reports have the information they need
- The impact of writing bad bug reports
- How to use consistency heuristics to describe why you feel this is actually a bug
Paul Holland is a Software Testing consultant and teacher. He is one of four instructors worldwide for the Rapid Software Testing course. Visit http://www.satisfice.com/info_rst.shtml for more information.
He was recently a Senior Director of Test Engineering at Medidata Solutions, Inc. in New York City. Previously, he was Head of Testing for over 2 years at a small consulting company and before that, he was an independent software testing consultant. From 1995 through 2012 he worked at Alcatel-Lucent (formerly Newbridge). During that time he worked primarily as a test manager in the DSL group, and on test automation of ATM switches – focusing on Switched Services, Cell Relay line cards, and Frame Relay line cards.
Software Testing Consultant;
Rapid Software Testing Teacher;
Managing – to produce effective software testing teams