Skip to content

All Flags Reference

Looking for example commands?

See every agent × tool × source combination → Command Combinations

/qa-pipeline flags

FlagRequired?Supported valuesDefaultNotes
--id <id>AlwaysIssue ID, file path, or comma-separated mixSingle: TEST-22, ./story.md · Multi: TEST-22,TEST-62, "QA-42,./spec.txt"
--source <src>Nogithub ✅, jira ✅, ado 🔜, linear 🔜(none — reads from file)Omit to read from a local file; provide to pull from an IMS
--repo <owner/repo>GitHub onlye.g. myorg/myrepoOnly needed with --source github
--tool <tool>Noplaywright ✅, restassured ✅, cypress 🔜, selenium 🔜playwrightCombine with commas: playwright,restassured
--tms <tms>Noxray, testrail, zephyr, markdownmarkdownOmit for local-only run. Add --tms xray to push to Xray
--no-prNo(flag only)(PR is created)Skip Draft PR phase
--url <url>NoAny URLFrom issue / .envOverride the UI URL
--api-url <url>NoAny URLFrom issue / .envOverride the API URL

/automate-from-tms flags

FlagRequired?Notes
--id <id>One of these three is requiredAutomate all TCs linked to this issue
--suite <name>One of these three is requiredAutomate a full suite by name
--case <ids>One of these three is requiredComma-separated TC IDs — most granular
--source <src>NoIssue tracker (for bug logging) — default github
--test-mgmt <tms>NoWhere to read TCs from — default markdown
--tool <tool>NoAutomation framework — default playwright
--bug-tracker <tracker>NoWhere to log bugs — defaults to --source value

Internal script flags (orchestrator sets these automatically)

These flags are only needed when calling individual scripts directly. The orchestrator (/qa-pipeline) sets them automatically.

FlagScriptNotes
--file <path>push-to-tmsPath to .md test case file
--results <path>update-tms-statusPath to .json results file
--run-id <id>TestRail onlyInteger run ID
--feature <slug>markdown TMS onlyShort slug string

TC selection priority (automate-from-tms)

--case > --suite > --id

Most granular wins.

Released under the MIT License.