Skip to main content
The Configuration tab shows the execution context for a test run. Use it to compare runs and find differences in code, CI, runner environment, or Playwright settings.

​
Source Control

Source control section showing branch, commit hash, author, message, and repository links
  • Branch, commit hash, author, message, timestamp.
  • Links to repository, commit, and PR.
Use this section to trace the exact code used for the run and reproduce from the same commit.

​
CI Pipeline

CI pipeline section showing provider, pipeline, build number, trigger, and environment
  • Provider, Pipeline, URL, Build #, and Trigger.
  • Env Name, Env Type, OS, and Node.js of the CI environment.
Use this section to confirm the test run is from the expected pipeline and compare it with other CI runs.

​
System Info

System info section showing host, CPU, memory, OS, Node.js and Playwright versions
  • Host, CPU, Memory, and OS.
  • Node.js and Playwright versions.
Use this section to spot runner differences between local and CI, or between CI environments.

​
Test Configuration

Test configuration section showing the projects table and workers, parallel, and browser settings
  • Projects: a table with each project’s Name, Base URL, Viewport, Trace, Video, and Screenshot settings.
  • Settings: Workers, Actual Workers, Parallel, Browsers, and Projects.
Use this section to reproduce the run and identify configuration drift across runs.

Summary

Group failures by cause

Specs

Review results by spec file

Errors

Group failures by the error that caused them

Analytics

Track reliability and duration trends over runs
Last modified on October 16, 2026