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
- Document test cases with Task Capture
- Parameters
- Playwright test case fields
- 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
- Accessibility testing for Test Cloud
- Running Autonomous Exploration
- Reviewing Autonomous Exploration results
- Project operations and utilities
- Test Manager settings
- ALM tool integration
- API integration
- Coding Agents for Testing
- Troubleshooting
Reviewing Autonomous Exploration results
Scenario findings, severity categories, and execution columns for reviewing an Autonomous Exploration run in Test Manager.
An exploration's results are organized by scenario. Each scenario includes a plain-language description of what was probed, plus a list of findings.
Findings
Each finding is tagged by:
- Category: Functional or UX.
- Severity: one of the following, with a rollup severity badge shown at the scenario level:
- Critical
- Severe
- Warning
- Info
Each finding expands to show:
- Expected behaviour versus observed behaviour.
- Screenshots.
- A Steps to reproduce section with a timestamped action and assertion log.
The execution header shows an aggregate findings count with a severity breakdown.
Navigating exploration runs
Past and in-progress runs are available under Execution > Exploration, with the following columns:
- Name
- Execution End
- Duration
- Status
- Created
Exploration results are kept separate from regular functional test results and are not synced to external application lifecycle management tools, such as Jira or Azure DevOps.