Our ping pong match begins with the tester serving the bug report to development. Unfortunately, the bug report is missing information that allows it to be reproduced and fixed. So, the dev returns serve by rejecting the bug as not reproducible. The tester hits the bug report back with a bit more information. This goes on and on until finally, the bug report gets enough information to allow the dev to fix the bug and win the point. Ping pong may be fun to play but it's a terrible way to report and fix bugs.

Come to this session and learn how writing good bug reports will stop bug report ping pong. We will start by discussing how bug report ping pong impacts your projects. We will then dive into writing a good bug report by learning how to describe observed and expected behavior, craft easy to follow reproduction steps, collect and capture environmental information and finally, write a summary that helps devs quickly identify and analyze the bug. It's time to put those bug report ping pong paddles away and this session will show you how.