Top errors

A top error is a group of a run’s failing tests that share the same error log. Groups are ordered by how many tests each one affected, so the largest cause comes first. For fields and response details, see the API reference.

List top errors

This command lists the run’s errors, most affected tests first. Use this when a run has many failures and you want to find the shared causes. In pretty output it prints a block per error rather than a table.

neetoplaydash top-errors list kftwnab --project pdqmxlz

Required arguments:

<run_id> - the run whose errors to group, 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

Sample output (--json)

{
  "data": [
    {
      "count": 3,
      "log": "TimeoutError: locator.click: Timeout 10000ms exceeded.",
      "test_entity_ids": ["vhrscje", "dhkscfj", "qmtzwbn"],
      "test_entities": [
        {
          "id": "vhrscje",
          "title": "adds an item to the cart",
          "spec": { "id": "bhkscfe", "title": "cart.spec.ts" },
          "project": "spinkart-web",
          "describe_path": ["Cart"]
        }
      ]
    }
  ],
  "breadcrumbs": [
    {
      "label": "Show test entity",
      "command": "neetoplaydash test-entities show <test_entity_id> --project <project_id> --run <run_id>"
    }
  ]
}

test_entity_ids names every test in the group. test_entities describes a capped subset of them, so on a large group the two differ in length - read any test beyond the described ones with test-entities show (get still works as an alias). The pretty format makes this explicit by printing a +N more line with the remaining ids. The error log is the grouping key with Playwright’s per-test Call log: section stripped, which is what lets tests that failed the same way land in the same group. The response is not paginated and returns at most 20 groups.

Getting started

Commands

List top errors

​List top errors

List top errors