About testdino-runs
A skill for inspecting automated test results with TestDino tools. It helps teams find runs by filters, examine individual test cases, and investigate failures using historical context.
Key features
- 01Find test runs with filters
- 02Inspect run details
- 03Review testcase failures
- 04Debug failures across historical runs
- 05Check project health when needed
Use cases
- 01Find failed runs on a branch
- 02Investigate flaky tests
- 03Summarize a test run
- 04Explore historical context for a failure
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ anthropics/ claude-plugins-community --skill testdino-runsAfter installing, type/testdino-runsin Claude Code to confirm it loaded.
Details
From the project READMETestDino Test Runs
Use TestDino tools when the user wants to inspect automated test results.
Preferred flow:
- Call
healthifprojectIdis not known. - Use
list_testrunsto find the relevant run. - Use
get_run_detailsfor one specific run. - Use
list_testcaseorget_testcase_detailsfor deeper failure analysis. - Use
debug_testcasewhen 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.
Comments
Markdown supported