← ClaudeAtlas

tms-uploaderlisted

Publishes scenario JSON as test cases into TestRail (or Zephyr Scale, Xray, qTest) with the agreed section hierarchy, priorities, labels, and requirement links, then writes the case IDs back into the automated tests so code and TMS stay linked. Use this skill whenever the user wants generated test cases in their test management system, whenever they ask to sync scenarios with TestRail, or as the delivery stage of the QA pipeline. Also use it to update previously uploaded cases without creating duplicates.
YevheniiaQA/qa-agent-toolkit · ★ 0 · AI & Automation · score 72
Install: claude install-skill YevheniiaQA/qa-agent-toolkit
# TMS Uploader The TMS is where the rest of the organisation sees QA work. Uploading is a projection of the scenario JSON into the TMS structure, done idempotently so re-runs update rather than duplicate. ## Disabled integrations Follow `qa-conventions` → *Disabled integrations* for the test management system (`testrail`, `zephyr`, `xray`, `qtest`): read `INTEGRATIONS`, skip a system that is not listed, report it as `➖ <system> disabled for this project`, never route around a `qa-guard` block. **Local alternative:** export the cases with manual-test-cases (CSV or XLSX in the format the TMS imports) and stop. Do not write case IDs back into the tests: there are none yet, and invented IDs are worse than missing ones. ## Before uploading **Refuse scenarios that have not passed the generator's quality gate.** Cases with placeholder data, missing expected results, or no traceability create mess that someone cleans up by hand later, and they undermine trust in everything the pipeline produces. **Confirm the section hierarchy first.** Use `TMS_ROOT_SECTION` from the project profile and the structure recorded in the working agreement. Generating a hierarchy the team did not agree to means someone drags two hundred cases between sections by hand. Three levels is the usual shape: ``` Platform / Auth / User login Platform / Integrations / Connect Confluence ``` ## Mapping (TestRail) | Scenario field | TestRail field | |---|---| | `testSuite.name` | Section (created if absent)