← ClaudeAtlas

caselisted

Create or update test cases in the Qase TMS (with a local-markdown fallback when Qase is unavailable). Use when asked to file test cases, write up regression cases from bug findings, or turn a described flow or an existing spec file into managed test cases.
sjzavala/claude-qa-tms · ★ 0 · Testing & QA · score 46
Install: claude install-skill sjzavala/claude-qa-tms
# File test cases in the TMS Input: **$ARGUMENTS** — may be findings from a prior `/qa-tms:explore` run, a described flow, a path to a spec file, or empty (then use the findings already in this conversation). ## Step 0 — Pick the backend Try Qase first. If the `qase` MCP tools are unavailable, or the first call errors on auth, **do not stop and do not debug the connection** — say one line ("Qase unreachable, writing cases locally to `test-cases/`") and switch to the local fallback in `references/local-cases.md`. Mention it once; don't re-litigate it later. ## Step 1 — Establish project context Call `qase_project_context` with the project `code` once — it returns the suites tree, milestones, environments, custom fields, and users in a single call, cached for 5 minutes. Cache that in your head for the rest of the session; don't re-fetch per case. No project code is hardcoded. Take it from the conversation if it's already unambiguous; otherwise ask which project to use **once**, then proceed. If you always work in one project, set it as the default here. Exact tool names and params are in `references/qase-tools.md` — the published Qase README lists names that don't exist on the shipped server, so use that file, not your memory. Step wording follows `references/case-authoring.md`: every step names the element by its visible label or role, and every expected result names an observable value. That is what makes `qa-tms:codegen` able to pick a selector mechanically instead o