testland/qase-io-case-management
Author and manage Qase.io test cases via the Public API v1 - create cases, organise into suites, attach structured steps, link to Jira/Linear/GitHub, manage shared steps, and bulk-import via JSON. Covers Token header auth, /case/{project_code} CRUD endpoints, the steps array with action / expected_result / data shape, and shared-step reuse. Use for pre-execution case authoring in teams using Qase as a modern lightweight TCM.
79
99%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
qase-api-reference.mdreferences/
Qase.io Public API v1 reference
Field enums, endpoint map, and response shapes for the Qase Public API v1. Per developers.qase.io schema definitions (Cloudflare-protected; cite by stable URL).
Field enums
| Field | Values |
|---|---|
severity | 1=Blocker, 2=Critical, 3=Major, 4=Normal, 5=Minor, 6=Trivial |
priority | 1=High, 2=Medium, 3=Low |
type | 1=Functional, 2=Smoke, 3=Regression, 4=Security, 5=Usability, 6=Performance, 7=Acceptance, 8=Compatibility (defaults; configurable) |
automation | 0=Manual, 1=Automated, 2=To-be-automated |
status | 0=Actual, 1=Draft, 2=Deprecated |
Map per severity-vs-priority-reference (in the qa-defect-management plugin);
note Qase priority is reversed from the defect-management convention (1=High
here vs 1=Critical in IEEE 1044).
Endpoints
| Verb + path | Purpose |
|---|---|
POST /case/{project_code} | Create a case |
PATCH /case/{project_code}/{id} | Update a case |
GET /case/{project_code}/{id} | Get one case |
GET /case/{project_code} | List cases (paginate with limit / offset) |
POST /suite/{project_code} | Create a suite |
POST /shared_step/{project_code} | Create a shared step |
POST /result/{project_code} | Post run results (different surface; not case authoring) |
Response shapes
- Create returns
{"status": true, "result": {"id": N}}. - List returns
{"status": true, "result": {"total", "filtered", "count", "entities": [...]}}. - Paginate a list until
len(entities) < limit.
Shared-step reuse
Define a step once, then reference it inside a case via its shared_step_hash:
steps = [
{"shared_step_hash": shared_step_hash},
{"action": "...", "expected_result": "..."},
]