- Release Notes Cloud Insights
- Getting Started
- Access and Permissions
- Notifications
- Interacting with Insights
- Action Center Integration
- Automation Hub Integration
- Autopilot integration
- Document Understanding Integration
- License monitoring integrations
- Test Manager Integration
- Real-time Monitoring
- Real Time Data Export
- Troubleshooting
Insights
Test Manager data model
The structure of the Test Manager data model is based on the following concepts:
|
Concept |
Description |
|---|---|
|
Explore |
The starting point for exploration. The data is surfaced via Explores, which you can think of as a general entity that corresponds to the fields within it. |
|
View |
A view represents a table of data, whether that table is native to your database or was created using Looker’s derived table functionality. Within each view are field definitions, each of which typically corresponds to a column in the underlying table or a calculation in Looker. |
|
Dimension |
As part of a View within the Explore, the Dimension is a groupable field and can be used to filter query results. It can be one of the following:
|
|
Measure |
As part of a View within the Explore, the Measure parameter declares a new measure (aggregation) and specifies a name for that measure. Examples of measures types:
integer,
string.
|
| Dimension | Type | Description |
|---|---|---|
| ProjectId | guid | The ID of the project. |
| TestExecutionId | guid | The ID of the test execution. |
| TestSetId | guid | The ID of the test set. |
| TestCaseLogId | guid | The GUID of the test case log. |
| TestCaseId | guid | Referenced the test case. |
| TestCase | string | A name for use on a chart <key>-<name>. This
is just a label for the TestCaseId.
|
| ExecutionType | enum (automated|manual|none) | The type of the execution:
|
| PackageName | string | The name of the automation package. |
| PackageVersion | string | The version of the executed package. |
| Machine | string | The name of the machine. |
| Executed By | string | The username or robot name who executed the test. |
| ReportingDate | date | The date when the test was executed. This is a date without time and also without time zone. |
| ReportingMonth (bin) | year-month | The calendar month extracted from the reporting date. |
| ReportingYear (bin) | string | The calendar year extracted from the reporting date. |
| TestCaseVersion | string | The version of the test case in Test Manager. |
| HasDefect | yes|no | Whether a test has a defect associated or not. |
| HasOpenDefect | yes|no | Whether a test has an open defect associated or not. |
| Measures | Type | Description |
|---|---|---|
| Total Count | integer | The total number of test case logs. |
| Passed Total | string | The number of passed test case logs. |
| Failed Total (technical) | integer | Technical results indicate results as failed when an exception occurs during execution. |
| Failed Total (functional) | integer | Functional or business results indicate results as none when an exception occurs during execution. |
| No Result (technical) | integer | Technical results indicate no results when an exception occurs during execution. |
| No Result (functional) | integer | Functional or business results indicate no results when an exception occurs during execution. |
| Total Runtime Technical | integer | Total technical runtime. |
| Total Runtime in Seconds | integer | Total runtime in seconds. |
| Total Pending Time in Seconds | integer | Total pending time in seconds. |
| Errors | integer | Number of test case logs which indicated an error during execution. |
| Error Rate (%) | number | Error rate with precision of 2 in percentages. |
