Real-Time Alerts Timestamped screenshots History Saved

Find out what broke, where, and when it happened

Each execution leaves a trace that can be analyzed: the step that failed, a screenshot of what the user would have seen, and the history. And the alert is sent to the channel you’ve chosen—not to all of them.

app.mrsuricate.com

Latest Campaign42 scenarios

WebsiteMobile appAPI

Web ·User LoginPast
Web ·Add to CartExpired
Web ·Payment ConfirmationFailed
API ·Order CreationCompleted

Last run 4 minutes ago

Attached screenshotAlert sent to the on-call team

A positive test result without evidence is useless

The team spends an hour trying to reproduce the incident before they can classify it, and sometimes they can't. On the other hand, an alert sent to everyone for every failure eventually gets filtered out by everyone.

Proof of Performance

Screenshot and details of the step that failed. You can see what the user would have seen, without having to manually replay the process.

Alerts by Severity

SMS for a critical incident in production, email to the team, and a webhook to Slack, Teams, or your on-call tool.

History and Evolution

Track changes in performance over time to identify performance degradation before your users do, rather than after.

One report per execution

The milestones achieved, the ones that didn't work out, the duration. That's what you bring up when someone asks what happened.

Which Channel for Which Severity Level

LocationChannelRecipientDeadline

Production-Blocking IncidentSMSOn-call dutyImmediate

Regression detected during acceptance testingEmail and webhookQA and Product TeamsAt the end of the run

Performance VarianceEmailTechnical ManagerPeriodic Report

GO FURTHER

Trigger RunsYour tests are launched by the pipeline, and the results are returned to the build.Handling IncidentsGrouping by cause and self-healing of selector failures.Accessibility testsRGAA and WCAG checks, executed and logged.

YOUR QUESTIONS

Questions We Get Asked About Reporting

Retained evidence, reporting channels, history: answers to the most frequently asked questions.

What evidence is retained after an execution?

A screenshot of the step where the failure occurred and a step-by-step breakdown of the scenario. This is what allows us to diagnose an incident without having to reproduce it manually.

Through which channels are alerts sent?

SMS for a critical incident in production, email for the list of workspace users, and webhooks to popular messaging platforms such as Slack or Teams.

Can we choose who gets what?

Yes, that's the idea. You adjust the sensitivity based on how critical the route is, to avoid a blanket alert that everyone ends up ignoring.

Are reports useful for compliance issues?

Accessibility and GDPR tests generate a dated history of the checks performed, documenting what was verified and when. This serves as a useful starting point to compare with the specific requirements of your audit.

How can you spot a problem that develops slowly?

Based on the execution history. A drift in response times or a scenario that fails once in ten attempts is visible in the series, not in a single execution.