74 integrations in 11 categories
TestingOps integrations
TestingOps turns your development and quality tools into context its AI test agents can use, and in supported workflows connects that context to test design, change impact analysis, execution, regression and reporting.
Featured workflows
Featured workflows
From Jira stories to test cases
User stories and acceptance criteria become the context agents write and review test cases from.
Model-aware testing for Mendix
The application model, not just the screens, informs which test cases are written.
Run cases and collect evidence
Test cases run on RunningOps with steps, results and evidence brought back to TestingOps.
Keep your test management tool
Send cases with steps to the tool your team already uses and learn from the cases already there.
How they connect
Kinds of connection
Not every connection works the same way. Each card and page names its kind, so you know whether TestingOps reads the tool, runs tests on it, calls it through MCP or is used from it.
Each integration page answers the same practical questions: what TestingOps reads from the tool, what it produces, where it can write back and under which conditions, how you connect it and what its limits are.
Connections differ. Some read and write through the tool's API, some are tools your agents can call over MCP, some read an exported file from a link, and some are setup guides for using TestingOps from another app. The labels on every card tell you which.
TestingOps connects to the tool with credentials you provide and reads or writes within what you allow.
A place where TestingOps runs your test cases and collects results and evidence.
Your TestingOps agents can call this tool through the Model Context Protocol (MCP) after you connect it. The tool does not send data to TestingOps on its own.
TestingOps reads an exported file from a link you give it, for example a file in a Git repository. There is no live connection to the source tool; changes arrive when the file at the link changes.
Agents run on your own AI provider account and API key instead of a shared one.
Lets test runs reach environments that are only open inside your network or VPN.
Use TestingOps from another app by connecting that app to TestingOps. This is a setup guide, not an installed connector.
Browse
All integrations
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.
Jira
Stories and acceptance criteria become test context; agents act on the workflow steps you choose and report back on the issue.
Native connectionAvailableGitHub
Issues, pull requests and the README become test context; agents work on issues through label-based board rules and file defects as issues.
Native connectionAvailableGitLab
Issues, merge requests and the README become test context; agents follow issue board lists and reply in notes.
Native connectionAvailableAzure DevOps
Work items and their Acceptance Criteria field become test context; agents act on state changes through service hooks.
Native connectionAvailable with limitsConfluence
The pages of a Confluence space become know-how that agents read when they write and review test cases.
Native connectionAvailableBitbucket
Pull requests, the README and repository files become test context; commits with Jira keys feed Jira impact analysis. Read-only.
Native connectionAvailable with limitsLinear
A team's issues become test context; agents read and update issues, and defects become Linear issues.
Native connectionAvailableYouTrack
Project issues become test context; agents comment, change State and tag issues; defects become YouTrack issues.
Native connectionAvailable
Test management
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.
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
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.
Figma
Turns each Figma screen into a knowledge-base document with its texts, controls and prototype links.
Native connectionAvailableMiro
Reads Miro board frames, sticky notes, cards and connectors as context for scenarios.
Native connectionAvailableZeplin
Reads handoff screens with annotations, designer notes and flow boards as context for test cases.
Native connectionAvailabledraw.io
Reads draw.io files from a link: shapes under their swimlanes and labelled arrows, page by page.
Exported file linkAvailable
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.
RunningOps.ai
Runs test cases with RunningOps' own engine and brings back verdicts, screenshots, video, logs and scripts.
Execution providerAvailableBrowserStack
Agents can call BrowserStack's hosted MCP tools; the direct Automate runner is switched off on testingops.ai.
Execution providerMCP tool for agentsAvailable with limits
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.
Mendix
Reads the Mendix app model so agents write test cases from entities, validation rules, pages and microflows.
Native connectionAvailableServiceNow
Stories, incidents, knowledge articles, catalog items and scoped app tables become test context; defects go back as records and ATF suites run on your instance.
Native connectionAvailablePower Apps
Reads model-driven apps and solutions from Dataverse: tables, forms, business rules and cloud flows. Canvas apps are not read.
Native connectionAvailable with limitsSalesforce
Reads objects, fields, record types, validation rule formulas, the new-record layout and flows, so agents test against the org's own rules.
Native connectionAvailableOutSystems
ODC: entities, screens, actions and roles through OutSystems MCP. OutSystems 11: environments, modules and version notes from LifeTime.
Native connectionAvailable with limits
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.
Camunda
Reads Camunda 8 Web Modeler files or deployed Camunda 7 processes and lists their paths as bounded test scenario candidates.
Native connectionExported file linkAvailableBizagi
Link a BPMN file exported from Bizagi Modeler; its lanes, gateways and events become bounded test scenario candidates.
Exported file linkAvailableSAP Signavio
Reads Process Manager BPMN models through an API user and turns their paths into bounded test scenario candidates.
Native connectionAvailableBPMN 2.0 file
Link a .bpmn file exported from any modeling tool; its paths, gateways and events become bounded scenario candidates.
Exported file linkAvailableIBM Blueworks Live
Exports Blueworks Live process blueprints as BPMN 2.0 through a Service ID and lists their paths as scenario candidates.
Native connectionAvailableCelonis Process Management
Reads processes of a Process Management storage (formerly Symbio) through its BPMN export; process mining data is not read.
Native connectionAvailableADONIS
Finds BPMN 2.0 business process diagrams in ADONIS repositories and turns their paths into bounded scenario candidates.
Native connectionAvailableFlowable
Reads the latest deployed process definitions through the Flowable REST API, or a .bpmn file link, and lists their paths as candidates.
Native connectionExported file linkAvailableARIS
Link BPMN files exported from ARIS, one by one or in bulk with a report script; their paths become scenario candidates.
Exported file linkAvailable
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.
Google Play
Play Console reviews become rating trends, version and device breakdowns, regression candidates and test ideas; history starts at the first sync.
Native connectionAvailable with limitsApple App Store
App Store reviews, read with an App Store Connect API key or from the public feed, become rating trends, themes and test ideas.
Native connectionAvailable with limitsHuawei AppGallery
AppGallery Connect comments become rating trends, APK version and phone model breakdowns, regression candidates and test ideas.
Native connectionAvailable
AI model providers
Choose the model provider your agents run on and use your own account and API key.
Anthropic Claude
Agents on your projects run Claude through your own Anthropic account and API key.
Model providerAvailableOpenAI
Agents on your projects run OpenAI models through the Codex adapter with your OpenAI API key.
Model providerAvailableGoogle Gemini
Agents can run on your Gemini API key, and Gemini CLI can use TestingOps over MCP: two separate connections.
Model providerConnection guideAvailableAzure OpenAI
Agents on your projects run on your own Azure OpenAI deployment through the Codex adapter.
Model providerAvailable with limitsxAI Grok
Agents on your projects run Grok with your xAI API key; Grok agents do not get MCP tools.
Model providerAvailable with limitsQwen
Agents on your projects run Qwen through OpenCode with your Alibaba Cloud Model Studio key.
Model providerAvailable with limitsKimi
Agents on your projects run Kimi models through OpenCode with your Moonshot AI key.
Model providerAvailable with limits
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.
Postman
Agents can work with the Postman collections, environments and workspaces your API key can see.
MCP tool for agentsAvailableDatadog
Agents can look up Datadog logs, traces, RUM and Synthetics around a failed run (US1 site).
MCP tool for agentsAvailable with limitsGrafana Cloud
Agents can query Loki, Prometheus, dashboards and alerts in your Grafana Cloud stack after you sign in.
MCP tool for agentsAvailable with limitsPagerDuty
Agents can check PagerDuty for an open incident before a failure is filed as a defect (US region).
MCP tool for agentsAvailable with limitsTestMu AI (LambdaTest)
Agents can reach HyperExecute results, SmartUI visual checks and accessibility tools on your TestMu AI account.
MCP tool for agentsAvailable with limitsSupabase
Agents can check test data and read logs in your Supabase projects, read-only.
MCP tool for agentsAvailableStripe
Agents can inspect sandbox payments, customers and disputes with a Stripe restricted key.
MCP tool for agentsAvailableAirtable
Agents can read the test-data tables in the Airtable bases your token allows, and update them with approval.
MCP tool for agentsAvailableCloudflare
Agents can look into zone settings, security rules and Workers logs when test traffic is blocked or fails.
MCP tool for agentsAvailableContext7
Agents can look up current documentation for the software libraries your application uses.
MCP tool for agentsAvailableMicrosoft Learn
Agents can search Microsoft's documentation and code samples for Azure, Dynamics 365, Power Platform and .NET.
MCP tool for agentsAvailableAWS Knowledge
Agents can search AWS documentation and check the regional availability of services and features.
MCP tool for agentsAvailableNotion
Agents can search and read the Notion pages you share, and write pages or comments with approval.
MCP tool for agentsAvailable with limitsmonday.com
Agents can read boards, items and docs and, with approval, add or update items on a bug board.
MCP tool for agentsAvailableIntercom
Agents can read support conversations, contacts and help articles as input for tests and defects (US workspaces).
MCP tool for agentsAvailable with limitsZapier
Agents can run the Zapier actions you enable on your Zapier MCP server, in the apps connected to Zapier.
MCP tool for agentsAvailable
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.
Claude
Add TestingOps to Claude as a custom connector, or to Claude Code as an HTTP MCP server, and work with runs, cases and defects from a chat.
Connection guideSetup guideChatGPT
Add TestingOps to ChatGPT as a custom MCP server and sign in, then ask about release readiness, existing cases and runs.
Connection guideSetup guideVS Code & Cursor
Add TestingOps to your editor's MCP configuration so its agent can read failing cases, check a change's impact and update cases.
Connection guideSetup guideMicrosoft Teams & Copilot
Build a Copilot Studio agent with TestingOps as its MCP tool and publish it to Teams and Microsoft 365 Copilot.
Connection guideSetup guideZoom
Your Zoom admin builds a Marketplace app that points at the TestingOps MCP server, so an AI Studio custom agent can ask about your tests.
Connection guideSetup guide
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.
RunningOps host in the network
Runs start on your own RunningOps host inside the network, so no VPN account, gateway or sign-in is needed.
Private networkAvailableGlobalProtect
A gateway machine signs in to your GlobalProtect portal with SSO, a password or a certificate and carries test traffic to internal addresses.
Private networkAvailableCheck Point Remote Access
A gateway machine signs in to your Check Point Remote Access VPN, asks for SMS or OTP codes in TestingOps and reconnects with a saved session.
Private networkAvailableCisco Secure Client (AnyConnect)
A gateway machine signs in to your ASA or FTD headend with a password, a client certificate or both; SSO is not supported yet.
Private networkAvailable with limitsFortiClient (SSL VPN)
A gateway machine signs in to your FortiGate SSL VPN with a password, or a certificate plus password, on the port and realm you set.
Private networkAvailable with limitsIvanti Connect Secure (Pulse)
A gateway machine signs in to your Ivanti Connect Secure appliance with a password or a client certificate, using your realm or sign-in URL path.
Private networkAvailable with limitsOpenVPN
Upload an .ovpn profile, optionally with a username and password; the gateway machine routes only the IP ranges you list.
Private networkAvailable with limitsWireGuard
Upload a WireGuard peer configuration; the gateway machine brings up the tunnel with wg-quick and routes the IP ranges you list.
Private networkAvailable with limitsIPsec (site-to-site)
IPsec site-to-site tunnels are available on request; the self-service form does not bring a tunnel up yet.
Private networkOn request
Not sure where to start?
Tell us which tools your team uses and where test cases come from today. A demo shows which of these connections apply to your projects and what they need from your side.