The testing report we forgot

The most important skill of a software tester is communication. Or at least majority of the conference attendees thought so at the EuroSTAR here.

What I’ve noticed however is that while testing professionals are good at bug centric communication, they easily forget the more important part.

Testers should learn to tell a story of how the results came to be. Easy way to experiment on your skill would be to answer this.

What would you report if no bugs were found in the session today?

Stop now. Really think about it for 60 seconds!

The story could begin by letting others in on the activities we engaged during this round.

We might want to tell them for example about the time allocated to activities like configuration, meetings, investigations, bug reporting and coverage.

But can you elaborate or even better, show which areas were covered and which were left out this time?

It’s obvious once we stop and think about it. But hard when we are engaged in the daily flow of action points.

That’s why I’d invite you now to outline a new storyline for the moment the limelight hits you the next time.

A pen, a paper and a short bullet journal might just make the difference for you to make a difference. So. 5 minutes.

Shall we?

Written by

Today the world doesn’t need your fear or your worry. Now, more than ever, it needs the best version of you!

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store