1

Our team is responsible for web application testing. We’ve recently faced a question of providing the most common (and what is more important, the most convenient and handy) format of displaying data in a detailed test report: pdf, email, html, excel, word, etc.

We would appreciate your sharing your experience and practice of representing detailed test results.

4
  • 1
    Who reads this report? What will they do with this report? What do they need to see? All communications need to be created with the recipient in mind. Sep 4 '13 at 12:21
  • You are right. We now mainly decided on its content. First we try to emphasize the cause of a test failure and show its location.
    – Anna
    Sep 4 '13 at 12:46
  • 2
    I think you are missing the point. If the report recipient needs to manipulate the data you send them in the report, .pdf format might be less useful than .xls (for example). The use case drives the format you should use. Sep 4 '13 at 12:49
  • A related question from the sidebar yielded an interesting link about testing dashboards that seems relevant, especially if your audience may not know what they want. It describes a general purpose approach that may give you some ideas to build on. Sep 4 '13 at 18:01
5

Since you seem to imply that you already know what data you are going to report on, why not have data populated real time and accessible via the intranet?

At MS all test results are available to everyone on the project team via the intranet. Test data is usually consumed across the organization differently, especially in large organizations. So, people can either get a high level view, or do a deep dive into key areas. Additionally, in some groups we have TV monitors in halls displaying dashboards of high level test data and project status.

Some teams also have weekly project mail summarizing overall status; including high level test status and "red flags."

2
  • Sure. We already provide test results in real time. We just thought that sometimes it might be useful to have test results not only in real time, but also published in another format.
    – Anna
    Sep 5 '13 at 10:53
  • Hope that your tast data is not exposed to other people out of the comany, or you do not significantly increase the risk with that approach.
    – Gaj Julije
    Mar 23 at 12:45
0

As a software qa services, reports are an integral part of testing i.e. it showcases the application stability. In order to showcase the reports for automated Web tests, we can use report generation tools such as TestNG Reporting Tool, Allure etc. However, in case we are testing the application manually, than we can showcase the report in the form of PPT or Excel charts format by showcasing the release details, Defects reported w.r.t. its Priority, Application wise defects reported, defect status [In Testing, In Development etc], regression testing details, total hours consumed etc.

Not the answer you're looking for? Browse other questions tagged or ask your own question.