Category ยท 3 integrations
App markets integrations
Store reviews show where real users struggle. TestingOps turns them into insights for the knowledge base: themes, version-level signals and test ideas.
Reading reviews is analysis, not testing: it tells you what to test next. Running those tests is a separate step on an execution provider.
Compare
How these tools differ
| Tool | What TestingOps does with it | Connection |
|---|---|---|
| Google Play | Reviews through the Play Developer API with a service account; the API returns only the last 7 days, so history builds up from the first sync. | Native connection Available with limits |
| Apple App Store | Two modes: an App Store Connect API key (90 days, no app version) or the keyless public feed (recent reviews with app version). | Native connection Available with limits |
| Huawei AppGallery | Comments through an AppGallery Connect API client from your app's data site, up to 90 days, with APK version and phone model. | Native connection Available |
Integrations in this category
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
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.
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.
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.