Category ยท 5 integrations
Low-code platforms integrations
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.
Each platform has its own building blocks. TestingOps reads the parts it can access and turns them into knowledge-base content for test case writing, in the platform's own terms. Reading never changes the application; ServiceNow is the one platform that can also receive defects and run ATF test suites.
Reading the model, writing test cases, producing automation and running tests are separate capabilities. Test cases are written by agents using the model as context, and run as AI-executed steps; each page states what applies.
Compare
How these tools differ
| Tool | What TestingOps does with it | Connection |
|---|---|---|
| Mendix | Reads the domain model, pages and page-called microflows; the only platform that also produces structured model facts and a coverage check. | Native connection Available |
| ServiceNow | Requirements, knowledge, catalog and app-model source in one connection; it also files defects as records and starts whole ATF suites on the instance. | Native connection Available |
| Power Apps | Dataverse model of model-driven apps and solutions, including business rules and cloud flows; canvas apps and Power Fx are not read. | Native connection Available with limits |
| Salesforce | Objects with validation rule formulas, record types, Apex trigger names and record-triggered flows, plus screen and autolaunched flows; Apex code is not read. | Native connection Available |
| OutSystems | Two depths: ODC entities, screens, actions and roles through OutSystems MCP; OutSystems 11 only the LifeTime inventory and version notes. | Native connection Available with limits |
Integrations in this category
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
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.
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.
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.
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.