Test Reporting in an Agile Context

Elizabeth Zagroba

j19sch@gmail.com

Half-day workshop - in English

It feels like test reporting is no longer a thing in Agile. As long as your team is delivering quality software at a steady pace, who cares about a big test report document? You’re working closely with your stakeholders as a team. It may seem like people don’t care about testing or quality, but the thing is, they trust you! 

But it doesn’t mean people don’t want to hear about the testing. In fact, you have a lot more opportunities to report about it. You’re telling people about what you did during stand-up. You reject a commit when you find a serious bug. Maybe you mention that the pipeline is red. And hopefully you talk as you’re pairing. With test reporting becoming more diffuse in this way, it may seem less valuable. But it doesn’t have to be. 

In this hands-on workshop, we’ll uncover some of the ways you are delivering information about the quality of your software and about how testing is going. We’ll outline who your stakeholders are, what information they care about, and what’s the best way to deliver this information. In short, we’ll explore the many different forms a test report can take, and how you can make them more effective.

Primarily for: Developers, Tester/test leads, Project managers, Managers, Scrum masters

Participant requirements: Nothing in particular.