Traces

A Playwright trace records everything the browser did during a test: the DOM at each step, network calls, console output, and screenshots. The CLI returns links that open those traces in Playwright’s viewer. For fields and response details, see the API reference.

List traces

This command lists trace viewer links for every test entity in a run, or for one entity when --test-entity-id is given. Use this when you want to step through a failure in the browser.

neetoplaydash traces list kftwnab --project pdqmxlz --test-entity-id vhrscje

Required arguments:

<run_id> - the run whose traces to list, from runs list.
--project <project_id> - the project the run belongs to.

Flag	Type	Required	Default	Description
`--project`	`string`	Yes		Id of the project the resource belongs to
`--test-entity-id`	`string`			Scope traces to a single test entity

Sample output (--json)

{
  "data": [
    {
      "test_entity_id": "vhrscje",
      "title": "adds an item to the cart",
      "trace_urls": [
        "https://trace.playwright.dev/?trace=https://assets-cdn.neetoplaydash.com/traces/abc123.zip"
      ]
    }
  ]
}

Each link points at trace.playwright.dev, Playwright’s hosted viewer, and carries a time-limited NeetoPlaydash URL for the trace file so the viewer can load it. That viewer is operated by Microsoft, not by NeetoPlaydash. Opening a link sends the artifact URL there.

The NeetoPlaydash part of the URL expires, so fetch links when you are about to open them rather than saving them for later.

Getting started

Commands

List traces

​List traces

List traces