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 in controlled availability, delivered only to eligible tenants. It 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.

字段	描述
来源	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.
标签	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 Selecting automation.