On this page

Notifications

In this section you will learn how to be notified by email, Slack, PagerDuty or webhook when a scheduled run fails or slows down.

Notifications are set per test, in the Notifications tab of Test Settings, and are sent for scheduled runs. A free license offers email notifications only; Slack, PagerDuty and webhook need a paid license.

Channels

Turn on one or more channels and fill in their destination. Each channel has a button that sends a test message, so you can check the destination before saving.

Channel Destination Test button
Email Notifications One or more recipients, added with Add Recipient Email. Needs the SMTP settings. Send Test Email
Slack Notifications A Slack Webhook URL, and optionally a Channel. Send Test Slack Message
PagerDuty Notifications The Integration Key of an Events API v2 integration on your PagerDuty service, and the Default Severity of failure alerts: Critical, Error (default), Warning or Info. Threshold alerts take their severity from the threshold status. Send Test Alert
Webhook Notifications A Webhook URL that receives a POST with a JSON body. Send Test Webhook

Triggers

Choose when to notify, under Notification Triggers:

Trigger Sends a notification when Default
Notify on Test Failure the test fails or errors on
Notify on Test Success the test passes off
Notify on Threshold Status Change the threshold status changes, for example ok → minor, minor → major or major → ok on
Notify on Threshold Exceeded the duration exceeds a threshold on

When a test has retries, notifications are sent once, after the last attempt.

Notify only on sustained slowness

A single slow run is often noise. Under Notify on Threshold Exceeded, tick Use “Notify After” conditions to notify only when both conditions are met:

  • Minimum Severity — Minor or worse, Major or worse (default) or Critical only
  • Consecutive Checks — the number of consecutive runs at that severity or worse (2 by default)

With Major or worse and 2 consecutive checks, a notification is sent only after 2 consecutive runs graded MAJOR or CRITICAL.

Webhook payload

The webhook receives a POST request with Content-Type: application/json, and must answer with a 2xx status within 30 seconds:


{
  "event": "test_result",
  "source": "Mugnsoft Pulse",
  "timestamp": "2026-10-23T08:15:02.120Z",
  "test": {
    "name": "search",
    "project": "web-shop",
    "suite": "smoke",
    "status": "FAILED",
    "duration": "12.48s",
    "durationMs": 12480
  },
  "threshold": {
    "status": "MAJOR",
    "exceeded": true
  },
  "execution": {
    "commandsExecuted": 7,
    "totalCommands": 9,
    "lastCommand": "click",
    "retryAttempt": 2,
    "retryCount": 2
  },
  "error": "Element not found: id=search"
}

status is PASSED, FAILED or ERRORED. threshold is present only when the threshold status is not OK, and error only when the run reported one.

See also

Translations

Retry