--kind. Only a test runs, so only a test has outcomes and attempts. A spec is the file its tests live in, so reading one returns the tests it contains rather than outcomes. For fields and response details, see the API reference.
List test entities
This command lists the specs or tests a run recorded. Use this when you want to go straight from a red run to the tests that made it red.<run_id>- the run whose entities to list, fromruns list.--project <project_id>- the project the run belongs to.
--kind is spec when omitted. --status takes a comma-separated list, each member exactly one of passed, failed, interrupted, timed_out, skipped, not_run, flaky, passing, failing, running, pending. This command defaults to 25 records per page rather than 15.
Sample output (--json)
title is the file name.
Show a test entity
This command shows one test entity with everything the run recorded for it. For a test that means the outcomes, the attempts inside each outcome, the Playwright error output, and time-limited links to the screenshots, videos, traces, and Lighthouse reports captured. For a spec it means the list of tests the run recorded in that file.get is still accepted as an alias for show.
<test_entity_id>- the entity to show, fromtest-entities list.--project <project_id>- the project the run belongs to.--run <run_id>- the run the entity was recorded in.
Sample output (--json)
outcomes and tests are complementary: a test fills outcomes and leaves tests empty, and a spec does the reverse, listing each contained test with its id, title, and status so you can read it individually.
Artifact URLs are time-limited. Fetch them when you are about to open them rather than storing them.
A test entity id must name an entity the given run recorded. One that ran only
in other runs is refused rather than returned with a placeholder status.