test-manager
latest
false
Test Manager user guide
- Getting started
- Project management
- Documents
- 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
- Manual test cases
- Importing manual test cases
- Document test cases with Task Capture
- Parameters
- Enabling governance at project level
- Disabling governance at project level
- Enabling governance at test-case level
- Disabling governance at test-case level
- Managing approvers for governed test cases
- Managing governed test cases in the In Work state
- Managing governeed test cases in the In Review state
- Managing governed objects in the Signed state
- Managing comments for governed test cases
- Applying filters and views
- Importing Orchestrator test sets
- Creating test sets
- Adding test cases to a test set
- Assigning default users in test set execution
- Enabling activity coverage
- Enabling Healing Agent
- Configuring test sets for specific execution folders and robots
- Overriding parameters
- Cloning test sets
- Exporting test sets
- Applying filters and views
- Accessibility testing for Test Cloud
- Running Autonomous Test Execution
- Reviewing Autonomous Test Execution results
- Searching with Autopilot
- Project operations and utilities
- Test Manager settings
- ALM tool integration
- API integration
- Coding Agents for Testing
- Troubleshooting
Header fields, tabs, and log details for reviewing an Autonomous Test Execution run in Test Manager.
A test execution triggered by Autonomous Test Execution shows its header fields, tabs, and logs.
Header fields
Execution identity:
- Result
- Type
- Source
Timing:
- Execution Start
- Duration
Tracking:
- Assignee
- Due Date
- Defect
Tabs
- Logs
- Robot Logs
- Execution details
- Affected requirements
Logs table
Each entry includes:
- Step
- Result
- Description
- Expected behaviour
- Tester comment
- Attachment
Each step expands into two parts:
- Sub-steps: the underlying action data, plus a zoomable and downloadable screenshot.
- Behaviour verification: the validation result data.
The Tester comment is generated automatically by the activity running behind the scenes.
Execution log
The setup pipeline runs through the following stages, in order:
- Policy validation.
- Package deployment to Orchestrator.
- Process creation.
- Robot connection check.
- Package install.
- Execution plan compilation.
It is followed by step-level agent reasoning during verification, such as locating the correct interface element or comparing expected and actual values.