Two-way exchange Five Connected Tools No duplicate entries

You keep your test management tool; we'll integrate with it

Xray, Squash, Xqual, Testomat, and Redmine are interconnected in both directions. Your test cases remain on your system, and the execution results are automatically uploaded there.

app.mrsuricate.com

SynchronizationTwo-way

WebsiteMobile appAPI

X-ray ·12 imported casesSynchronized
Squash ·Recipe CampaignSynchronized
Xray ·Payment ProcessFailure reported
Redmine ·Ticket createdSynchronized

Last run 4 minutes ago

Result reportedNo manual entry

The real cost is having to enter the data twice

Your test cases live in Xray or Squash; your repository is there, and so are your campaigns. If automation lives in a separate tool, someone copies the data over, then forgets to update it, and the two repositories diverge within three sprints. This isn’t a tool issue—it’s a boundary issue.

Two-way exchange

We read your test cases directly from your tool and report the results of each run back to it. No need to manually re-run an export.

Your reference framework remains the standard

You continue to create and organize your cases right where your teams are already working. Nothing has to be moved.

Five tools at the same level

Xray, Squash, Xqual, Testomat, and Redmine—with no hierarchical relationship between them and no half-baked integration.

And the rest via API

A tool that isn't on the list is triggered via an API call. This is the same mechanism used for triggering it from your CI/CD pipeline.

Traffic in both directions

WHAT'S COMING FROM YOUFrom your tool to the platform

The test cases in your repository
The area to be covered, block by block
Campaigns and Their Composition
The identifiers for your requirements, when you have them

WHAT GOES BACK THEREFrom the platform to your tool

The status of each execution, whether successful or failed
The exact step where the script failed
A screenshot of what the user would have seen
Timestamps, to track the series

The result: a single source of truth—yours—and no one has to manually copy execution statuses anymore.

GO FURTHER

Other Features

Every component of the platform, from scenario creation to verification of its execution.

No-code scenario editorAI-assisted capture or block-based assembly. Recreate your user flows without writing any code.Learn more Continuous Testing & CI/CDOn-demand, scheduled, or triggered by your CI/CD, and grouped into campaigns.Learn more Maintenance & AI-powered self-healingSelector failures partially resolve themselves, and incidents are grouped by cause.Learn more Reporting, Incidents & EvidenceThe failed step, the capture, the history. And alerts sent via the channel of your choice.Learn more Test DataVariables, datasets, and separate environments. One scenario, multiple profiles.Learn more Integrations & APIsOver 1,000 connectable tools: CI/CD, tickets, messaging, on-call systems.Learn more Security & Data SovereigntyDeveloped and hosted in France, AES-256 encryption, GDPR and DORA compliance.Learn more BenefitsHow automation impacts your acceptance testing timelines, production regression testing, and your team’s workload.Learn more OverviewAll the platform’s components on a single page, with use cases by business line.Learn more

Is there a term you don't understand? The automated testing glossary defines it.

YOUR QUESTIONS

Questions We Get Asked About Interconnection

Purpose of the exchange, tools covered, reference framework: answers to the most frequently asked questions.

Should we stop using Xray or Squash to automate with Mr Suricate

No, that's the opposite of how it works. Your test management tool remains in place and continues to fulfill its role. The platform connects to it to run tests and report the results back to it.

In which direction does information flow?

Both. The test cases and scope come from your tool, and the execution status, the step that failed, and the screenshot are sent back to it.

Which tools are actually interconnected?

Xray, Squash, Xqual, Testomat, and Redmine are all on the same level. There are no primary integrations and no secondary integrations.

Who remains the authority on the test framework?

Your tool, if that's what you want. In fact, that's the most common approach: teams continue to create and organize their cases right where they already work.

What if our tool isn't on the list?

It integrates via an API call, using the same mechanism as triggering from a continuous integration pipeline. Tell us about your tool, and we'll work together to see what's feasible.