# Testdino Runs

> Use when the user wants to inspect automated test runs, list failed or flaky tests, debug a faili…

Use when the user wants to inspect automated test runs, list failed or flaky tests, debug a failing testcase with historical context, or filter runs by branch, commit, author, environment, browser, status, or tags. Includes list_testruns, get_run_details, list_testcase, get_testcase_details, and debug_testcase.

- Page: https://ss33.ai/skills/anthropics/testdino-runs-89394782116
- Publisher: anthropics
- Category: [Software Development](https://ss33.ai/skills/category/software-development-t44z8z) › [Testing & QA](https://ss33.ai/skills/category/software-development-t44z8z/testing-and-qa-g56s6z)
- License: MIT
- Source: https://github.com/anthropics/claude-plugins-community/blob/06ec7b6a0a82bdc4bec44bd82d4368c42f20d7c1/testdino/skills/testdino-runs/SKILL.md

## Skill

SKILL.md: https://ss33.ai/api/v1/ss33/download/anthropics/testdino-runs-89394782116

# TestDino Test Runs

Use TestDino tools when the user wants to inspect automated test results.

Preferred flow:

1. Call `health` if `projectId` is not known.
2. Use `list_testruns` to find the relevant run.
3. Use `get_run_details` for one specific run.
4. Use `list_testcase` or `get_testcase_details` for deeper failure analysis.
5. Use `debug_testcase` when the user wants historical debugging context for a failing test.

Good requests for this skill:

- show failed runs on a branch
- inspect flaky tests
- summarize one test run
- debug a failing testcase with history

Common filters from the docs:

- branch
- time interval
- author
- commit
- environment
- status
- browser
- error category
- tags

Use `list_testruns` first when the user does not already know the exact run ID or counter.
Use `debug_testcase` when the user wants root-cause analysis and recommendations across historical runs, not just a single-run snapshot.
Use `health` at the start of a session when the project is still ambiguous.