Category ยท 6 integrations
Test management integrations
Keep your test management tool as the system of record. TestingOps can send cases with their steps, bring existing cases into its knowledge base and report run results where the tool supports it.
Most teams already have years of test cases in a test management tool. TestingOps reads those cases so agents do not write duplicates, and sends new or revised cases back in the tool's own structure.
Each tool below lists what is read, what can be written and under which conditions. Writing is an explicit action, not a background sync.
Compare
How these tools differ
| Tool | What TestingOps does with it | Connection |
|---|---|---|
| TestRail | The most complete test management connection: scheduled import of suites and sections, push into sections, write-back and duplicate removal with backups, and run results. | Native connection Available |
| Xray | Cloud or Server / Data Center; creates new tests and Test Executions, but does not update or delete tests that already exist. | Native connection Available with limits |
| Zephyr Scale | Zephyr Scale Cloud only: creates and updates cases in folders and reports test cycles; steps are read for the first 200 cases, and cases cannot be deleted. | Native connection Available with limits |
| Azure Test Plans | Reads stop at 200 cases; writes cases into suites of a test plan TestingOps manages, test runs and Bug work items, and can delete duplicates. | Native connection Available with limits |
| Qase | Cloud API by project code: suites, cases with steps, completed runs and defects; suite trees beyond 100 suites may lose folder paths. | Native connection Available with limits |
| qTest | Strongest in the write direction: cases into modules and runs as test cycles with logs; bulk reads may come without steps, and skipped results are logged as failed. | Native connection Available with limits |
Integrations in this category
TestRail
Import suites and sections with their steps, push cases into sections, write edited cases back and report runs as TestRail runs.
Native connectionAvailableXray
Reads Xray tests with steps, creates new Manual tests in repository folders and reports runs as Test Executions.
Native connectionAvailable with limitsZephyr Scale
Reads Zephyr Scale Cloud cases, creates and updates cases in folders and reports runs as test cycles.
Native connectionAvailable with limitsAzure Test Plans
Reads Test Case work items, writes cases into a suite tree, records test runs and files Bug work items.
Native connectionAvailable with limitsQase
Reads cases with suite path and steps, writes cases into suites, records completed runs and files defects in Qase.
Native connectionAvailable with limitsqTest
Writes cases into qTest modules and records runs as test cycles with test logs; bulk reads may lack steps.
Native connectionAvailable with limits
Other categories
Issue trackers, wikis and code
Requirements, work items, documentation and code changes are where test design starts. These connections give TestingOps agents that context and, where supported, a place to report back.
Design tools
Screens, flows and workshop boards describe the intended behaviour before any code exists. These connections bring that material into the knowledge base that agents write test cases from.
Test execution
TestingOps runs test cases on an execution provider and brings back results, steps and evidence. Which providers a workspace can use is decided by its execution policy.
Low-code platforms
Low-code platforms keep the application as a model: data, screens and logic in a structured form. Reading that model lets agents design tests around what the application actually contains.
Process models (BPMN)
A business process model already describes the paths a case can take. TestingOps turns BPMN 2.0 elements into bounded test scenario candidates for review.
App markets
Store reviews show where real users struggle. TestingOps turns them into insights for the knowledge base: themes, version-level signals and test ideas.
AI model providers
Choose the model provider your agents run on and use your own account and API key.
MCP tools for agents
These connections run in one direction: your TestingOps agents call an external tool through the Model Context Protocol (MCP) when a task needs it.
Connection guides
Use TestingOps from the apps you already work in. These are setup guides: you connect the app to TestingOps, and the app calls TestingOps.
Private networks
Many test environments are only reachable inside a company network. These options let test runs reach them without opening the environment to the internet.