Result histories commands

The result-histories command lets you view how a test entity performed across recent runs.

List result history

This command shows a test entity's status history across runs. Use this when you want to check whether a spec is flaky or consistently failing.

neetoplaydash result-histories list gc432cw fj6qmpa wjn5ymm
neetoplaydash result-histories list gc432cw fj6qmpa wjn5ymm --days 14
neetoplaydash result-histories list gc432cw fj6qmpa wjn5ymm --started-at 2025-01-15

Required arguments:

• <project_id> - Project identifier

• <run_id> - Run identifier (anchor run)

• <test_entity_id> - Test entity identifier

Optional flags:

• --days - Number of days to look back from the anchor date (default 7)

• --started-at - ISO anchor date to count back from (e.g. 2025-01-15)

• --subdomain <name> - Target a specific logged-in workspace

• --json - Return JSON envelope output

• --quiet - Return raw payload only

• --toon - Return TOON (token-optimized) output

Sample output:

STATUS   DURATION   RUN ID    STARTED AT              
──────   ────────   ───────   ────────────────────────
flaky    338        x7kmp3n   2025-12-29T15:03:24.000Z
failed   299        f4gjw6q   2025-12-30T03:43:00.000Z
failed   258        h8rst2z   2025-12-30T15:03:34.000Z
flaky    354        m3npq7v   2025-12-31T03:12:57.000Z
failed   169        k6xyz4w   2025-12-31T15:04:06.000Z