- 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
Packaging Playwright projects for Test Manager
Package a Playwright test project into a UiPath automation package and publish it to Orchestrator so Test Manager can execute it.
This capability is available in Test Manager only when delivered through Test Cloud.
Package a Playwright test project into a UiPath automation package (.nupkg) and publish it to Orchestrator, so the automation becomes available for execution from Test Manager.
Prerequisites
- A self-contained Playwright test project directory: its own
playwright.config.*,package.json, and a supported lockfile, with dependencies resolvable at the packed root. A mono-repo subfolder works only if it's self-contained. - Playwright version 1.19 or later. npm is the only supported package manager — the packed root must contain a
package-lock.json. - The UiPath Command Line Interface (CLI) installed and updated to a recent version. See Installing UiPath CLI.
- A Test Manager project key. Required by default — the CLI refuses to pack without one unless you pass
--no-create-test-cases. Matching test cases are auto-created and auto-linked once Test Manager ingests the resulting package, not at packaging time. The key must be uppercase alphanumeric.
Packaging excludes node_modules, .git, .uipath, dist, test-results, playwright-report, and .cache. It also always excludes secret files at any depth: .env, .env.*, .npmrc, and .git-credentials. Everything else in the project directory ships as-is, so keep secrets out of other files — hard-coded credentials in config or fixture files still ship.
Steps
-
Open a terminal in the Playwright project's root directory.
-
Run
uip tm packwith the--type playwrightoption, for example:uip tm pack --project-path . --type playwright --project-key SWAG --name SwagLabsDemo --package-version 1.0.0 -o .packages --output jsonuip tm pack --project-path . --type playwright --project-key SWAG --name SwagLabsDemo --package-version 1.0.0 -o .packages --output jsonFor the full flag reference, including how to opt out of test-case auto-creation, see uip tm pack.
-
Publish the resulting
.nupkgto the tenant's Orchestrator Package Feed, using one of the following:- Upload it manually in Orchestrator (Packages > Upload).
- Drop it into a folder Orchestrator watches for packages.
- Use the UiPath CLI to upload it directly from the command line.
Result
The package appears in the Package Feed in Orchestrator. If a project key was supplied, matching test cases are auto-created in that Test Manager project, with the Playwright automation already linked. Otherwise, the package's automations become available for selection through Selecting automation.
Related articles
- Playwright test automation
- uip tm pack
- Playwright test automation with the uipath-test skill — automate this entire flow, including packaging, from a coding agent.