Reports
QMetry Test Management for Jira offers more than 30 reports to serve the varied reporting purposes like evaluating the current status of the project and quality of the product, tracking manual and automation testing efforts. The QA Manager can add these reports to the dashboard to share with all stakeholders. The various filters provided to customize the reports and obtain the desired statistics. The reports can be further drilled down by exporting it in an excel sheet.
Report Name | Description |
|---|---|
Test Case Reports | |
The report shows a summary of test cases grouped by their workflow status/priority/component/label. | |
The report shows a summary of Manual vs Automated test cases based on testing type. The test type is determined by how a test case is created in QMetry for Jira. Test Cases that are created in QMetry for Jira via Automation (Automation API, Maven automation, Jenkins automation, Bamboo automation) will have the type as "Automated". Test Cases that are created manually or via Open API or imported through Excel into QMetry for Jira will have a type of "Manual". | |
The report shows a summary of the test cases planned or unplanned for execution. Test cases that are linked with test cycles are "Planned" for execution. Test cases that are not linked with test cycles are considered "Unplanned" for execution. You can find out test cases that are yet not part of any test cycle and add such test cases to test cycles. | |
The report shows a summary of test cases associated with defects captured during execution. The report can be filtered based on different combinations of Test Cycle and Test Plan. The defects linked to the test step level are also considered for this report. | |
Test Execution Reports | |
The Test Case Execution Summary helps the testing team, the project manager, and the product owner understand the status of testing and the stability of the overall application. The report shows the count of test cases passed, blocked, failed, not executed, and so on. The report can be grouped by Label, Component, Environment, Build, Test Cycle, Requirement, Project, Test Case Type, andAssignee. | |
The report provides comparison between the Estimated Time for test case execution vs. Actual Time taken for test case execution. | |
The report displays Assignee wise summary of Estimated Time vs. Actual Time of test case execution. It shows the actual time taken by the Assignee to whom the test case was assigned for execution. | |
Defect Reports | |
The Defect Summary report displays details related to defects logged to test cases. The defects can be organized by Workflow Status, Priority, Project, Environment, and Build. | |
The Resolved Issue Verification tabular report provides issue traceability. Issues are displayed with their associated test plan, test cycle, test case, build, and environment. | |
The report displays a bar stack chart for Defects that are linked in execution. | |
Traceability Reports | |
The Traceability Report has been designed to enable you to trace relationships among Requirements, Test Cases, Test Cycles, and Defects. | |
Coverage Reports | |
The Coverage By Requirement report displays the coverage relationship between Stories and Test Cases. For the selected Project, the Coverage Report shows which stories have one or more test cases associated with them. | |