- Getting Started
- Studio
- Orchestrator
- Testing robots
- Test Manager
Reports
Understand the progress, detect problems at a glance, and review KPIs through the reports.
The following report types are available:
- Dashboard reports that provide daily and weekly breakdown of test results, including passed/failed ratio, test execution list, and KPIs, such as the total coverage, or open defects.
- Reporting service through ODBC or native SQL Server connections, so you can use the reporting tool of your choice to create custom reports and additional dashboards.
You can examine the reports of each project individually. To view dashboard reports, open Test Manager and select a project from the list to view the Dashboard page.
|
Section Number |
Report |
Description |
|---|---|---|
|
1 |
Results |
Bar chart displaying the results of your test runs. To switch between daily and weekly views, click the focus indicator, at the upper-right side of the dashboard and choose an option from the dropdown. The weekly report goes back 14 weeks. |
|
2 |
Current Day/Week Indicator |
Day/Week indicator of the results shown in the bar chart. |
|
3 |
KPIs |
Open Defects is available only for connected projects. For example, defect reporting from the Jira project connected to Test Manager. The number of defects defined with the highest priority in Jira are shown in the Critical section. You can click the hyperlink to open the Jira filter. If you unlink a connection, Open Defect will not be shown anymore. Total Coverage The percentage of requirements that have at least one test case out of the total number of requirements. Automation Rate The percentage of test cases without automation/manual steps defined, as well as the automated, and manual test cases, respectively. |
|
4 |
Latest Results |
Latest test executions that contributed to your test results displayed in the bar chart. |
For example, you have a high number of defects that need to be dealt, alongside an equally high number of manual test cases.
You can glance over the dashboard to check the number of defects, where you can click on the Critical section within the Open Defects report, to open the filter in Jira. The Automation Rate report tells indicates the degree of automation of your test project. Using this information, you can start reducing the number of manual test cases, so that automated test cases come ahead, and allocate more testers to deal with the high number of defects.
The following table lists the views which are available for reporting purposes. Your system administrator can help you to connect your reporting solution to those views. You can either use native SQL connections or, if your reporting tools do not support this, you can use an ODBC connection. For more information, see ODBC Data Source Administrator Help - Windows Data Access Components.
The following read-only views are accessible through a special user role via ODBC.
|
Column Name |
Data Type |
Description |
|---|---|---|
|
ID |
GUID |
Automatically generated ID for the project. |
|
Prefix |
string |
The prefix of the project, as added when it was first created. |
|
Project Name |
string |
The name of the project, as added when it was first created. |
|
Column Name |
Data Type |
Description |
|---|---|---|
|
Name |
string |
The name of the test execution. |
|
Project ID |
GUID |
The ID of the project this Test Execution was assigned to. |
|
Execution Start |
date/time |
The start of the execution. Please note that pending Test Executions have a
NULL value.
|
|
Execution Finished |
date/time |
The time when the execution finished. Please note that pending Test Executions have a
NULL value.
|
|
Column Name |
Data Type |
Description |
|---|---|---|
|
ID |
GUID |
Automatically generated ID for the test case. |
|
Name |
string |
The name of the test case as added when it was created. |
|
Type |
set |
Can have one of the following values:
|
|
Column Name |
Data Type |
Description |
|---|---|---|
|
Test Case ID |
GUID |
Automatically generated ID. |
|
Test Execution ID |
GUID |
Automatically generated ID for the test execution. |
|
Test Case Version |
string |
The version added when a test case is created, if added. |
|
Result |
ENUM |
Can have one of the following values:
|
|
Execution Start |
date/time |
The start time of the test case execution. |
|
Execution End |
date/time |
The end time of the test case execution. |
|
Executed By |
string |
There are two possible values:
|
|
Column Name |
Data Type |
Description |
|---|---|---|
|
ID |
GUID |
Automatically generated identifier. |
|
Object Key |
string |
Automatically generated identifier which contains the project key and an automatically incremented number. |
|
Name |
string |
The name of the requirement as added when it was created. |
|
Description |
string |
The description of the requirement as added when it was created. Accepts markdown. |
|
Project ID |
GUID |
Automatically generated ID for the project. |
