Convert testing data into valuable project information.

Joel Montvelisky wrote an interesting piece on the art of transforming testing data into project information. In his article he showed different examples of test execution reports and explained why report B was better than report A. He noted that when you work with people outside of your testing team, you must also think like them, understand the information they need and how to to display it in a way that they will grasp the content faster and better. 

Here are some examples of test execution reports:

Team A’s Report:
Total Tests in Cycle: 376 
Passed Tests: 301
Failed Tests: 28 

Tests not Run: 57

Team B’s Report:
Tests in Cycle: 376
Execution percentage: 87.5%
Passed percentage: 80%

Which report is better?

While both reports are providing the same data, report B supplies the readers with better information. The advantage that report B has on report A is that it shows the percentages in their report. This is an advantage because people don’t like doing math equations in their heads, when they can just read it like in Team B’s report.  The less people need to think, the more brilliant your report will appear to the intended audience.

Key tips for test execution reports

  • Show data in percentages or rates
  • Use graphs
  • Don’t pollute the report with useless data
  • Anticipate questions
  • Report should speak for itself. Less explanations = good report.

Read More



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s