Use when the user wants to manage a manual execution run or update case-level results inside a run — listing runs, creating runs for a release, inspecting a run, assigning cases, or marking case results (passed/failed/blocked/skipped/retest/untested). Accepts counter-style IDs like RUN-12 and TC-156.
Instalación
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Use when the user wants to manage a manual execution run or update case-level results inside a run — listing runs, creating runs for a release, inspecting a run, assigning cases, or marking case results (passed/failed/blocked/skipped/retest/untested). Accepts counter-style IDs like RUN-12 and TC-156.
TestDino Manual Runs
Use TestDino manual-run tools when the user wants to manage a manual execution run or update case-level results inside a run.
Preferred flow:
Call health if projectId is not known.
Use list_manual_runs to discover runs by name, state, release, environment, or tags.
Use get_manual_run to inspect one run's metadata and rollup stats.
Use create_manual_run or update_manual_run for run-level metadata changes.
Use list_run_test_cases before changing any individual case in a run.
Use update_run_test_case to assign a case, change its result, or update elapsed time.
Important details:
runId accepts an internal ID or a counter-style ID like RUN-12.
rtcRef can be the run test case row ID, case key like TC-156, or the underlying test case ID.
updates.assigneeUserId can be a user ID or email address.
updates.result accepts display form or canonical form, but canonical values like passed, failed, blocked, skipped, retest, and untested are safest.
For create and update payloads, tags and linkedIssues must be JSON arrays.
