QA.tech + TestRail
The TestRail integration connects your TestRail instance (instance URL, account email, API key) so the QA.tech agent can look up and work with your existing test-management data from chat. The instance must be reachable over HTTPS on a public address; internal-only instances are not supported.
What you can do
- Look up TestRail cases for a suite from chat
- Keep an authoritative external test inventory aligned with QA.tech activity
- Ground new tests in cases you already documented
Set it up
Connecting TestRail
- 01
Generate an API key in TestRail for the account QA.tech should use.
- 02
Add the instance URL, account email, and API key in QA.tech's Integrations settings.
- 03
Ask the agent for a suite's cases in chat to confirm the connection.
Full reference in the QA.tech docs.
Where teams use this
TestRail in practice
Teams with years of documented cases in TestRail use this for traceability: generated tests reference the documented case, and the external inventory stays the system of record while execution moves to agents. It also keeps a critical-path regression plan honest, since the plan maps to named cases rather than tribal knowledge. Documented cases map cleanly onto executed end-to-end flows, which is what auditors and new hires actually ask for.
FAQ
Common questions
- Can I connect a TestRail instance on our internal network?
- Not directly; the instance must be publicly reachable over HTTPS.
- Do I need Custom MCP for TestRail?
- No, TestRail is built in. Custom MCP is for services without a native integration.
Related integrations
Trello
Next →Xray
Your team moves fast. Can your testing keep up?
QA.tech agents test your product autonomously, so moving fast never means shipping broken. See how it works in a 30-minute demo.