- Getting started
- Project management
- Working with Change Impact Analysis
- Create test cases
- Assigning test cases to requirements
- Cloning test cases
- Exporting test cases
- Linking test cases in Studio to Test Manager
- Delete test cases
- Enabling governance at project level
- Disabling governance at project level
- Enabling governance at test-case level
- Disabling governance at test-case level
- Enabling or disabling governance in bulk for test cases
- Enforcing signing order for governed test cases
- Managing approvers for governed test cases
- Managing governed test cases in the In Work state
- Managing governed test cases in the In Review state
- Managing governed objects in the Signed state
- Managing comments for governed test cases
- Viewing governance information for test case logs
- Managing approvers for governed test case logs
- Managing governed test case logs in the In Work state
- Managing governed test case logs in the In Review state
- Managing governed test case logs in the Signed state
- Managing comments for governed test case logs
- Enabling governance at test case log level
- Disabling governance at test case log level
- Viewing and searching test cases
- Project operations and utilities
- Test Manager settings
- Tenant level settings
- General project settings
- Events
- Subscribing to events
- Subscribing to all events
- Unsubscribing from events
- Unsubscribing from all events
- Unsubscribing from the Notifications settings page
- Viewing notifications
- Filtering notifications
- Viewing email notifications
- Enabling email notifications for SMTP servers
- Viewing only unread notifications
- Marking all notifications as read
- Clearing all notifications
- Deleting notifications
- Customer managed keys encryption
- Audit logs
- ALM tool integration
- ALM tool integration
- Test Manager Connect
- Test Manager - Integration Service connector
- Outbound IP ranges for connectors
- Working with SAP Cloud ALM and Test Manager
- Step 1: Integrating SAP Cloud ALM with Test Manager
- Step 2: Creating automated test cases in SAP Cloud ALM
- Step 3: Creating automated test cases in Test Manager
- Step 4: Synchronizing test cases from Test Manager to SAP Cloud ALM
- Step 5: Assigning test automations to test cases
- Step 6: Executing test cases
- SAP test automation best practices
- Troubleshooting the Jira integration
- API integration
- Coding Agents for Testing
- Troubleshooting
Test Manager data model
Reference for the Test Manager data model terms, dimensions, and measures used to build Insights dashboards.
This reference lists the Explores, views, dimensions, and measures of the Looker-based data model behind Insights dashboards, with tables of the available dimensions and measures. Availability depends on the cloud platform you use.
Terms and concepts
The structure of the Test Manager data model is based on the following concepts.
Explore
The starting point for exploration.
The data is surfaced via Explores. An Explore is 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 the derived table functionality of Looker.
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:
- An attribute, which has a direct association to a column in an underlying table.
- A fact or numerical value.
- A derived value computed based on the values of other fields in a single row.
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 .
Dimensions and measures
Feature availability depends on the cloud platform you use. For details, refer to the Test Manager feature availability page.
The Requirements, Test sets, and Test executions dimensions and measures are available in Test Manager only when delivered via Test Cloud.
Test case logs
The following tables describe the available dimensions and measures for test case logs.
| Dimension | Type | Description |
|---|---|---|
| Assignee Email | string | The email address of the user to which a test case was assigned to. |
| Automation Project Name | string | The name of the automation linked to the test case. |
| Due Date | date | The date when a manual test case was scheduled to have been executed. |
| Execution Start | date | The date when the test execution started. |
| Executed By | string | The username or robot name who executed the test. |
| Execution End | date | The date when the test execution ended. |
| Execution Type | string | The type of the execution: Automated for automated tests, Manual for manual tests, or None for test cases that are not executed and are in the Pending state. |
| Host Machine Name | string | The name of the machine. |
| Project Name | string | The name of the Test Manager project. |
| Project Prefix | string | The prefix of the Test Manager project. |
| Reporting Date | date | The date when the test was executed. This is a date without time and also without time zone. |
| Result | string | The test case result: Passed, Failed, or None. |
| Robot Name | string | The name of the robot that executed the test. |
| Test Execution Name | string | The name of the test execution. |
Table 2. Test Case Logs measures
| Measures | Type | Description |
|---|---|---|
| Total Count | integer | The total number of test case logs. |
| Passed Count | string | The number of passed test case logs. |
| Failed Count (Technical) | integer | Technical results indicate results as failed when an exception occurs during execution. |
| No Result Count (Technical) | integer | Technical results indicate no results when an exception occurs during execution. |
| Duration in Seconds | integer | Total runtime in seconds. |
Requirements
The following tables describe the available dimensions and measures for requirements.
Table 3. Requirement dimensions
| Dimension | Type | Description |
|---|---|---|
| Project Name | string | A combination of the project name and project prefix aimed to make it unique and increase readability. |
| Name | string | A combination of the requirement key and its name, aimed to make it unique and increase readability. |
Table 4. Requirement measures
| Measure | Type | Description |
|---|---|---|
| Total test case count | integer | The number of test cases assigned to a requirement. |
| Automated test case count | integer | The number of automated test cases assigned to a requirement. |
| Manual test case count | integer | The number of manual test cases assigned to a requirement. |
| Passed test case count | integer | The number of test cases assigned to a requirement that have passed in the latest test run. |
| Failed test case count | integer | The number of test cases assigned to a requirement that have failed in the latest test run. |
| None test case count | integer | The number of test cases assigned to a requirement with no result in the latest test run. |
| Total requirements count | integer | The total number of requirements. |
Test sets
The following tables describe the available dimensions and measures for test sets.
For assigned test cases, the test set view contains information about static test assignments.
Table 5. Test set dimensions
| Dimension | Type | Description |
|---|---|---|
| Project Name | string | A combination of the project name and project prefix aimed to make it unique and increase readability. |
| Name | string | A combination of the project name and project prefix aimed to make it unique and increase readability. |
| Robot name | string | The name of the robot that executed the test set. |
| Source | string | The source of the test set: Orchestrator or Test Manager. |
Table 6. Test set measures
| Measure | Type | Description |
|---|---|---|
| Total test set count | integer | The number of test sets. |
| Automated test case count | string | The number of automated test cases in the test set. |
| Manual test case count | integer | Number of manual test cases in the test set. |
Test execution
The following tables describe the available dimensions and measures for test executions.
Table 7. Test executions dimensions
| Dimension | Type | Description |
|---|---|---|
| Project Name | string | A combination of project prefix and name to make it unique and increase readability. |
| Name | string | A combination of execution ID and name to make it unique and increase readability. |
| Test set name | string | A combination test set key and name to make it unique and increase readability. |
| Execution type | string | The execution type: Manual, Automated, None, or Mixed. |
| Source | string | The source of the execution: TestManager, Orchestrator, or Studio. |
Table 8. Test execution measures
| Measure | Type |
|---|---|
| Total test execution count | integer |
| Manual execution type count | integer |
| Automated execution type count | integer |
| Mixed execution type count | integer |
| Duration in seconds of test execution | integer |