Skip to content

Alarm and Notifications

TestCLIX lets you configure Error evaluation and notifications per test. These settings determine both:

  • when a test’s status changes to Error
  • when notifications are sent

This helps you:

  • quickly detect failing tests
  • monitor long-term reliability trends
  • receive alerts before failures impact users

Each test can have independent error evaluation parameters and notification preferences.

When the number of failed executions reaches your defined threshold, TestCLIX:

  1. marks the test’s status as Error, and
  2. sends notifications (if enabled) via your configured channels (for example, email or Slack).

Two main parameters control error evaluation:

  • Evaluation period — defines how many recent executions are taken into account (from 1 to 50 runs).

  • Failures to alarm — defines how many failed runs must occur before triggering a notification (from 1 to 50).

If the evaluation period is set to 10 and failures to alarm is 3, an alert will be sent only if 3 errors occur within the last 10 runs.

This approach helps reduce false alarms caused by temporary issues such as network instability or third-party dependencies.

  1. Navigate to Workspace using the left sidebar menu.

  2. Click the Create button on the right side.

  3. Select Website Availability.

  4. Scroll down to the Advanced options section.

  5. Expand the Alarm & Notifications subsection.

  6. Enable Error notifications.

  7. Set the following parameters:

    • Evaluation period — number of runs used to assess failure trends (1–50).
    • Failures to alarm — number of failures required to mark status as Error and trigger notifications (1–50).
  8. Save your configuration.

    Error notification configuration

After saving, TestCLIX will begin evaluating test results and send alerts according to your thresholds.