Skip to main content
A run is one execution of a project’s Playwright suite, reported by CI. Runs carry the commit, branch, author, tags, and status, plus the aggregate pass/fail counts. For fields and response details, see the API reference.

List runs

This command lists the runs recorded for a project, newest first. Use this when you start triage: filter to the branch and the status you are chasing.
Required arguments:
  • <project_id> - the project whose runs to list, from projects list.
--status takes exactly one of running, passed, failed, passing, failing, timedOut, interrupted. The server caps this endpoint at 50 records per page. A larger --page-size prints a warning on standard error, and the server clamps the page to 50. Check pagination.page_size in the response for the size actually applied.
Sample output (--json)
Every run the project holds is listed, including one that reported no test attempts at all. Such a run still carries its commit, branch, and status, but its run_statistics is empty and test-entities list reports nothing for it.

Show a run

This command shows one run with its summary, aggregate statistics, and the spec files it executed, each with the tests grouped under it. Use this when you want the shape of a whole run in a single call rather than paging through its test entities. get is still accepted as an alias for show.
Required arguments:
  • <run_id> - the run to show, from runs list.
  • --project <project_id> - the project the run belongs to.
Sample output (--json)
The specs list is paginated, and its pagination object sits inside data alongside it. See the API reference for the full response.