-
Notifications
You must be signed in to change notification settings - Fork 52
Description
Problem to solve (from the user’s perspective)
Use case: I want to extract test plans and cases from TestRail to convert them into automated tests (e.g. Playwright). Right now this requires dropping down to raw curl calls against the REST API, which defeats the purpose of having a CLI.
How could we improve this?
Requested commands (or similar):
trcli get_plans --project-id N
trcli get_plan --plan-id N
trcli get_suites --project-id N
trcli get_cases --project-id N --suite-id N [--section-id N]
trcli get_case --case-id N
Output: JSON to stdout, consistent with how other trcli commands report results.
Why this matters: A complete CLI should support both directions — pushing results in and pulling test definitions out. Read commands would make trcli useful for test generation workflows and AI-assisted automation
Primary value dimension
Productivity — less time to achieve the task
If you selected “Other”, describe the value dimension
No response
Where is the limitation?
CLI — behaviour/UX/flags issue
CLI version (fill if CLI is involved)
No response
TestRail version/edition (fill if API is involved)
No response
What improves, and by how much?
Looking to increase use of this cli tool for all interactions with testrail
KPI(s)
New feature
Urgency
Critical — revenue or contractual risk
Proposal (CLI-level sketch)
Requested commands (or similar):
trcli get_plans --project-id N
trcli get_plan --plan-id N
trcli get_suites --project-id N
trcli get_cases --project-id N --suite-id N [--section-id N]
trcli get_case --case-id N
Output: JSON to stdout, consistent with how other trcli commands report results.
Why this matters: A complete CLI should support both directions — pushing results in and pulling test definitions out. Read commands would make trcli useful for test generation workflows and AI-assisted automation