Blog
 

Top 5 QMetry Reports for Test Management and Actionable Insights

Jatin Lala
April 19, 2021
Banner Gain Actionable Insights

QMetry includes many reports out of the box that are categorized under the “QMetry System Reports” section. These reports are designed keeping in mind all the QA best practices, to give the product managers, scrum masters, QA managers, and testers the data that is most relevant. This enables them to make important decisions for the ongoing project and understand the current state of the testing progress.

System Reports are divided into separate dashboards as per different modules viz. My Dashboard, Requirement Report, Test Case Report, Issue Analysis, Issue Trend, Top Issues Report, Execution Summary Report, Traceability, and so on. These dashboards can be exported to a PDF or can be scheduled to be emailed to the desired stakeholders. The report gadget charts can also be exported to a variety of formats like PNG, JPEG, PDF, XLSX, SVG document, etc. or the raw report data to CSV. The report data can be filtered with great flexibility by different projects, desired date range, release, cycle, statuses, and assignees as needed. You can also create your own custom dashboards by adding the top reports that you refer daily and set them as default when you login to QMetry.

Here are our 5 favorite reports which give great insight about your project health.

  • Test Execution Assignments
  • Execution Summary Report (Dashboard)
  • Test Execution Summary by Folder
  • Traceability Report
  • Top Issues Report

1. Test Execution Assignments

Test Execution

The Test Execution Assignments report gadget is useful for testers whose role is to perform daily test executions. This report appears for each tester on their “My Dashboard” and tells them the scope of the executions that need to be performed which are assigned to them by their managers.

The report gives a list of test executions that are assigned to the tester along with complete details. The testers can just click on the Execute button in the report to begin executing the test case which opens the test execution page.

2. Execution Summary Report (Dashboard)

The Execution Summary Report dashboard gives important details and summary about the project’s executions and the issues identified during the executions. Some important reports gadgets in this dashboard are listed below.

  • Test Case Execution by Assignees – This report shows the scope of work assigned to each tester and the current progress made. It also makes it very easy to identify the test cases that are planned but still unassigned.Test-Case-Execution-by-Assignees

    There are times when a QA manager is monitoring multiple projects managed by different testers or teams. The test case execution by assignees report quickly enables QA managers to see the number of test case executions performed by different testers along with their execution status in one or more projects. The report chart can be drilled down further with a click for detailed information.

  • Test Suites Execution Summary – The Test Suites Execution Summary report displays the execution summary of test suites grouped by the execution status of its test case runs. This report shows the detailed progress of every test suite planned for a sprint or a cycle. It is very helpful for QA Leads and Managers as they can view the execution status of test cases under individual test suites quickly without opening each test suite.Test-Suite-Execution-Summary

    This report gadget is designed to help QA Managers to identify the number of test cases that are in passed, failed, not run, or any other status for each test suite that out of the total number of test cases and platforms linked. The additional details about the total number of platforms and total number of test cases columns in report adds more value to the report.

  • Test Case Execution Result – This report is designed for the stakeholders and QA managers who would want an overall glimpse of the scope and state of testing progress.
    Test-Case-Execution-Result

    The same report can be utilized to see the testing state of the project for testing of a release and cycle. The report chart can be drilled down further with a click for detailed information.

3. Test Execution Summary by Folder (Dashboard)

QMetry facilitates grouping of similar test cases for executions in a test suite. The test suites signify executions to test a specific user scenario, or a feature being tested. The test suite folders are often used to group similar test suites on basis of functional areas, modules, component, or release-cycles. The Test Execution Summary by Folder report helps you to know the number of test cases and their status for every test suite folder in the project.

Test-Execution-Summary-by-Folder

This report is helpful when the stakeholders or QA managers are looking for reports of a specific module, component or a product area which are grouped by such test suites folders. This report can be further drilled down to the last level up to the test suite of a sub-folder relating to its sub-module or sub-functional area.

The execution details are also available at the level of test suite in the next report on the gadget showing the number of test executions of the test suite with their folder details, number of linked platforms, test cases grouped by their status, with counts and percentages making it easy to identify the maximum or minimum status percentages in every test suite.

  • Top Issues Report

    The issues that are repeatedly observed and linked with more executions are usually the ones that need immediate attention from the product development teams. Product teams often decide which issues need to be addressed first based on their priority and severity. However, they also need to consider the issues being reported frequently across various test executions that need to be addressed and have blocked testers in multiple executions.

    Top-issues-report

    When testers link existing issues to the executions, they may not be aware about the other executions that are also impacted by the same issue. The top issues report facilitates this by listing down the issues sorted by the number of executions they have been linked with. Also, this report helps the testers to start their re-testing by focusing on the issues that impacted more executions.

  • Resolved Issue Verification

    Issues reported during the testing are fixed in the newer builds for a given release. Such issues need to be re-verified by testers to ensure they have been resolved as a part of the release.

    Resolved-Issue-Verification

    The Resolved Issue Verification report lists out the issues that have been marked as resolved by the development teams. The report simply looks for the statuses that are deemed as resolved in the project configuration and lists out the issues.

5. Traceability Report

Saving the best for the last! This report is most loved by all the QMetry customers. We believe any reporting without the detailed traceability presented by QMetry would be incomplete. This report is heavily used by product managers, scrum masters and QA managers alike to check the completeness of user story. There are teams that refer to this report during their daily scrums, sprint reviews and testing progress meetings at a given point of time.

Traceability-Report

QMetry acts as a repository of all the assets that are created from its inception throughout the software development and testing lifecycles. Stories are managed in the requirements module, linked with test cases to test those requirements. The test cases are further grouped for executions when linked to test suites. Under different test suite executions, the test cases are marked with a status and relevant defects and tasks are linked to them.

The traceability report gives complete trace of the test assets from the requirement to its execution and linked defects. The traceability can be generated by Requirements, Test Cases, Issues or Executions. For example, a Trace by Requirements would have the selected requirement(s) linked to its relevant test case(s) executed under its respective test suites with their status and issues found during the testing for a given platform, release, and cycle combination.

Conclusion

Different types of test reports provide actionable insights to agile teams to help understand the project health and product-readiness for go-to-market. QMetry’s in-depth reporting features out-of-the-box reports built for QA teams that include traceability, reusability, coverage etc. In addition, users can leverage QMetry Insight to generate deep dive capabilities, advanced reports that help users save queries/reports as gadgets and easy to use custom dashboards.

See QMetry’s Reports in action by signing up for Free Trial.
Sign me up for Free Trial

5 4 votes
Article Rating

Let’s get you started with QMetry®

Get Started
Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments

Trusted by teams across the globe for 10+ years

The QMetry brand is trusted by 1000+ customers globally across Finance, Healthcare, Travel, Hospitality, Retail, Education and many more.
These are just some of our customers.
Loading...