How Playwright artifact capture works

Screenshot, video, and trace capture for Playwright test executions in Test Manager, governed by your project's own Playwright configuration.

Note:

This capability is in controlled availability, delivered only to eligible tenants. It is available in Test Manager only when delivered through Test Cloud.

Test Manager doesn't override how a Playwright project is configured to capture screenshots, videos, and traces. Your project's own configuration always wins: Playwright resolves capture settings (use: { screenshot, video, trace }) with the project-level playwright.config.ts taking priority over any platform-level toggle.

Whatever artifacts a Playwright project already produces for a test are what show up in Test Manager. Capturing more artifacts, for example traces on every run, is a matter of adding the setting directly to playwright.config.ts:

use: { trace: 'on' }

For the steps to change and republish this configuration, see Configuring artifact capture for Playwright tests.

Setup and dependency tests

If a Playwright project uses dependencies between projects, for example an authentication setup that must run before a test, Test Manager runs that setup automatically as part of the dispatched test and shows it as part of the same result. This is different from Playwright's fixture system (test.extend()), which Test Manager doesn't model — see Playwright test automation.

Playwright attempts and traces

Each test case log for a Playwright execution gets two additional tabs beyond the standard ones Test Manager exposes:

• Attempts displays each entry Playwright made per attempt, on that test case's log. Expanding an attempt shows a headline of what went wrong, and expanding further renders the full error context — this is Playwright's own error-context.md file, rendered inline rather than requiring a download.
• Trace displays an embedded Playwright trace viewer, so you can inspect console logs, network calls, and attachments for that attempt without leaving Test Manager. Robot logs from the native execution are found in the existing Logs tab instead, which shows the same robot logs for every test case log in a Playwright-based execution.

Additional files are attached where Playwright produces them: console-output.txt and console-errors.txt per test, and a per-test playwright-result.json. The raw, whole-run results.json is attached at the execution level. Attachments can be downloaded individually, or viewed natively through the trace viewer.

Retries

If a project has retries configured and a test fails but then passes on retry, Test Manager records the result as Passed, with the failed attempt(s) still visible in the Attempts drill-down described above. Artifacts from failed attempts are kept, since they're the most useful for debugging.

Video rendering

Test Manager doesn't render Playwright's .webm video recordings inline as a playable video — the same behavior as for native UiPath automations today. The trace viewer links to the .webm file per attempt, where it can be downloaded.

Related

• Playwright test automation
• Configuring artifact capture for Playwright tests
• Analyze test results