Open APIOutgoing WebhooksAccommodations in France

Integrations & APIs: Integrate testing into your workflow

Launch campaigns from your CI/CD pipeline via API; receive results in Jira, Slack, via SMS, or via webhook; view your test cases in Xray, Squash, Xqual, Testomat, or Redmine. Results are delivered right where your teams are already working—not in yet another interface.

app.mrsuricate.com
Execution Results Real-time data streams
CI/CDAlertsTicket System
  • CI/CD ·GitLab PipelineTriggered
  • Alert ·Slack channel #qaSent
  • On-Call Duty ·Run Team SMSPending
  • Ticket ·Jira MSU-482Created
Last webhook sent 40 seconds ago
Result ReportedJira MSU-482 updated

Results need to be where your teams are looking

A test that fails in an interface that no one opens is useless. The point of integration isn't the technical connection—it's ensuring that the right person is notified through the right channel, with enough context to take immediate action.

Mouse icon

Triggering from your CI/CD

A generic API launches your campaigns from GitLab, Jenkins, Azure DevOps, or any orchestrator—including a custom-built tool. A failed test can block deployment to production.

Purple Rectangles Icon

Email, Slack, text message, or webhook. The channel and recipient are configured on a per-scenario basis depending on the severity, ranging from a simple notification to an on-call alert.

Purple Gear Icon

Jira and your other ticketing tools receive the incident along with the failed step, the screenshot, and the history. No more manual copy-and-paste between two interfaces.

Purple API Test Icon

Xray, Squash, Xqual, Testomat, and Redmine: the platform reads your test cases and logs the results of each execution back into them. You don't have to maintain two separate repositories.

What a Truly Connected TV Can Do

Without integration
With Mr Suricate
Failure is evident in an interface that no one opens.
The alert comes in on the channel the team is already monitoring.
The deployment proceeds even when the acceptance test fails.
A failed test can prevent the system from going live.
The ticket is copied by hand and is often incomplete.
The ticket starts with the failed move and the capture.
Test cases exist in duplicate, in two tools.
The reference system remains yours; the result is fed back into it.
Each new tool requires dedicated development.
A generic API and outbound webhooks are all that's needed.
No one knows who is responsible for handling the incident.
The recipient is determined in advance based on criticality.
ResultInformation flows without human intervention: the campaign starts in your pipeline, the result is sent back to your test repository, and the alert is sent to the person who can take action.

TEST MANAGEMENT

Your test cases remain in your tool

Xray, Squash, Xqual, Testomat, and Redmine are interconnected in both directions: the platform reads your test cases and reports the results of each execution back to them, including any failed steps. You don't have to maintain two separate repositories.

X-raySquashXqualTestomatRedmine
How Interconnection Works

YOUR QUESTIONS

Questions We Get Asked About Integrations

APIs, CI/CD, alerts, and test management: answers to the most frequently asked questions.

Are there native connectors for GitLab, Jenkins, or Azure DevOps?

Triggering is done through a generic API, not through a dedicated plugin for each orchestrator. Your pipeline calls the API to launch a campaign, then retrieves the result. This is more flexible than a connector: the same integration works regardless of your tool, including an in-house orchestrator.

Can a failed test prevent a release?

Yes. Your pipeline reads the campaign results and makes a decision. You choose which scenarios are blocking and which remain informative: critical paths on one hand, secondary checks on the other.

Through which channels are alerts sent?

Email, Slack, SMS, and webhooks. The channel and recipient are configured on a case-by-case basis depending on the level of urgency: a simple notification for a secondary check, an SMS to the on-call team for a payment process.

Should we stop using our test management tool?

No. Xray, Squash, Xqual, Testomat, and Redmine are interconnected in both directions: the platform reads your test cases and reports the results of each execution back to them, including any failed steps. Your repository remains yours.

What if the tool we're using isn't on the list?

The API and outbound webhooks cover this scenario. Any tool capable of calling an API or receiving a webhook can trigger a campaign and receive its results. For special cases, our teams will work with your teams to manage the integration.

Watch it play on your TV

A 30-minute demo. We'll launch a campaign from a pipeline and watch the results appear in your tool.