Result histories

A result history is one test entity’s status in each earlier run inside a look-back window, alongside the commit and branch of the run it came from. For fields and response details, see the API reference.

List result histories

This command lists a test entity’s past results, counting back from an anchor date. Use this when you want to tell a new failure from a long-standing flake.

neetoplaydash result-histories list vhrscje --project pdqmxlz --run kftwnab --days 14

Required arguments:

<test_entity_id> - the entity whose history to read, from test-entities list.
--project <project_id> - the project the run belongs to.
--run <run_id> - the run the entity was recorded in.

Flag	Type	Required	Default	Description
`--days`	`int`		`0`	Number of days to look back from the anchor date (default 7)
`--project`	`string`	Yes		Id of the project the resource belongs to
`--run`	`string`	Yes		Id of the run the resource belongs to
`--started-at`	`string`			ISO anchor date to count back from (e.g. 2025-01-15)

The window is --days long and ends at the anchor date. The anchor is --started-at when given, and otherwise the time the entity executed in the run you named, so the default reads backwards from the run you are already looking at.

The flag table shows --days defaulting to 0. That is the flag’s unset value, not a zero-day window: left at 0 the CLI omits the parameter and the server applies its own default of 7 days. Pass a positive number to widen or narrow the window.

Sample output (--json)

{
  "data": [
    {
      "status": "failed",
      "duration": 3.21,
      "started_at": "2026-06-27T09:14:25.000Z",
      "run_id": "kftwnab",
      "run": {
        "commit_name": "Fix flaky checkout spec",
        "branch": "main",
        "author": "Oliver Smith",
        "tags": ["nightly"],
        "commit_id": "9fceb02e1d2c4bb6a1f3f6b0c8e7d5a1b2c3d4e5",
        "ci_build_id": "gh-actions-4821",
        "duration": 182.45,
        "status": "passed"
      }
    }
  ]
}

The response is not paginated, so the window size is what bounds it. A wide --days on a busy project returns a lot of entries.

Getting started

Commands

List result histories

​List result histories

List result histories