JSON reporter output configuration
JSON reporter produces an object with all information about the test run. Use PLAYWRIGHT_JSON_OUTPUT_NAME environment variable when running with --reporter=json, or pass outputFile option in configuration file.
ci
199 notes in this subject, read out of this brain and free to use. This is page 4 of 4.
JSON reporter configuration options
JSON reporter configuration options: PLAYWRIGHT_JSON_OUTPUT_DIR (no config option) specifies directory to save output file, ignored if output file is specified, defaults to cwd or config directory; PLAYWRIGHT_JSON_OUTPUT_NAME or outputFile (both refer to same thing) specifies base file name relative to output dir, defaults to printing JSON report to stdout; PLAYWRIGHT_JSON_OUTPUT_FILE (use outputFile instead) specifies full path to output file, if defined PLAYWRIGHT_JSON_OUTPUT_DIR and PLAYWRIGHT_JSON_OUTPUT_NAME are ignored.
JUnit reporter output configuration
JUnit reporter produces a JUnit-style XML report. Use PLAYWRIGHT_JUNIT_OUTPUT_NAME environment variable when running with --reporter=junit, or pass outputFile option in configuration file.
Blob reporter fileName option
The Blob reporter now accepts a fileName option to specify the name of the report file to be created.
Reporter.onEnd includes startTime and duration
The Reporter.onEnd method now reports startTime and total run duration for the test execution.
Reporter.onExit method
The Reporter.onExit method is called when the reporter exits, allowing cleanup of reporter resources.
HTML reporter host and port options
The HTML reporter now accepts host and port options to configure where the reporter is served, e.g., reporter: [['html', { host: 'localhost', port: '9223' }]].
grep and grepInvert CLI options combined with config
Command line options --grep and --grep-invert are now applied together with grep and grepInvert options specified in the config, allowing fine-grained test filtering.
Ubuntu ARM64 support
Playwright 1.17 supports Ubuntu 20.04 ARM64, allowing tests to run inside Docker on Apple M1 and Raspberry Pi.
Blob reporter outputFile option
The Blob reporter now allows overriding the report file path with a single outputFile option. The same option can also be specified as PLAYWRIGHT_BLOB_OUTPUT_FILE environment variable.
JUnit reporter includeProjectInTestName option
The JUnit reporter now supports an includeProjectInTestName option to include project name in test identifiers.
--last-failed CLI option runs only previously failed tests
The --last-failed command line option runs only the tests that failed in the previous test run, allowing for quick re-testing of fixes.
--project wildcard filter
The --project command line flag now supports wildcard matching with '*' to filter projects by name pattern, e.g., npx playwright test --project='*mobile*'.
Run TypeScript compiler alongside Playwright in CI
For GitHub Actions CI, run `npx tsc -p tsconfig.json --noEmit` before `npx playwright test` to check types separately, since Playwright does not perform type checking itself.
reuseExistingServer pattern for CI environments
Set reuseExistingServer to !process.env.CI to allow the local dev server to be reused when running tests locally, but start a fresh server in CI environments.
Trace on CI configuration
Traces should be run on continuous integration on the first retry of a failed test by setting `trace: 'on-first-retry'` in the test configuration file. This produces a trace.zip file for each test that was retried.
Recommended test runner for JavaScript/TypeScript
For JavaScript and TypeScript, the built-in Playwright test runner is the recommended way to run end-to-end tests for the best experience.
Playwright JavaScript/TypeScript has built-in test runner
Playwright for Node.js comes with its own test runner that provides parallelization, screenshot assertions, HTML reporter, and automatic tracing.
WebView CI workflow configuration
.github/workflows/tests_webview_simulator.yml runs WebView tests on macos-15 with booted iOS Simulator and ios-webkit-debug-proxy (via brew install ios-webkit-debug-proxy). Triggers: workflow_dispatch and pull_request only when paths under tests/webview/**, the webview/ source folder, or the workflow file itself change.