- スタート アップ ガイド
- プロジェクト管理
- ドキュメント
- 変更影響分析を使用する
- テスト ケースを作成する
- テスト ケースを要件に割り当てる
- テスト ケースを複製する
- テスト ケースをエクスポートする
- 実行用のテスト ケースを設定する
- Studio Web でテスト ケースを自動化する
- How Playwright artifact capture works
- Packaging Playwright projects for Test Manager
- Configuring artifact capture for Playwright tests
- Studio のテスト ケースを Test Manager にリンクする
- テスト ケースを削除する
- 手動テスト用のテスト ケース
- Task Capture でテスト ケースを文書化する
- パラメーター
- Playwright test case fields
- フィルターとビューを適用する
- Test Cloud のアクセシビリティ テスト
- プロジェクトの運用とユーティリティ
- Test Manager の設定
- ALM ツールとの連携
- API 連携
- テスト用エージェントのコードを作成する
- トラブルシューティング
Package a Playwright test project into a UiPath automation package and publish it to Orchestrator so Test Manager can execute it.
This capability is in controlled availability, delivered only to eligible tenants. It 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.
前提条件
- 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.
手順
-
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.
結果
The package appears in Orchestrator's Package Feed. 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.
関連
- Playwright test automation
- uip tm pack
- Playwright test automation with the uipath-test skill — automate this entire flow, including packaging, from a coding agent.