- 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
Playwright test case fields
Fields and system labels populated on a Test Manager test case when it's linked to a Playwright automation, and how data-driven Playwright tests map to test cases.
This capability is available in Test Manager only when delivered through Test Cloud.
The following fields are populated on a test case when a Playwright automation is linked to it. For the end-to-end flow that populates them, see Playwright test automation.
| Field | Description |
|---|---|
| Source | Playwright or UiPath. |
| Test case name (Playwright format) | Spec file path, then the full Playwright describe-ancestry plus test title — as opposed to the Studio format (folder path + name). Capped at 255 characters. See Selecting automation. |
| Project / spec file | The Playwright project and spec file the test belongs to, captured as metadata on the test case. One test case is created per Playwright test — there's no fan-out into multiple test cases when a test matches more than one configured Playwright project. Project selection for execution happens at the test set level, not through multiple test case rows. |
| Labels | Auto-populated from Playwright annotations (for example, resilience, observability), usable for filtering and for scoped test set membership. |
PW_ system labels
Linking a Playwright automation automatically adds a set of system labels to the test case, prefixed PW_:
PW_File_…PW_Path_…PW_Project_…PW_Suite_…PW_Tag_…PW_Annotation_…
These labels are created on link and removed on unlink; labels added manually are left untouched. Dynamic test sets and the --labels filter of the UiPath Command Line Interface (CLI) match label names exactly (case-sensitive).
Data-driven (parameterized) tests
Each variation generated by a Playwright data loop is created as its own test case. Adding any single data-driven variation to a test set runs all variations of that test, not just the one added.
Re-execution
Re-running an execution reuses that execution's frozen snapshot: the same package, version, and project selection it was created with. See Playwright projects for test sets.