Hypertest Docs
HyperTestKnowledge Base
  • Quick Set-up
    • Install HyperTest
    • Deploy your application
    • Mirror Traffic
      • Using Kubernetes
      • Using Amazon ECS
      • Using Docker
      • Using Nginx
      • Using Goreplay
        • ElasticBeanStalk Script for Goreplay
      • Using Apache
      • Using IIS
      • Using Istio
      • Using Kong
      • Using HAProxy
      • Others
  • HyperTest Overview
    • Introduction
    • Architecture
  • Detailed Setup Guide
    • Detailed Setup Guide
      • Installation
        • Linux VM
        • Kubernetes Cluster
          • Hardware Requirements
          • Cluster Setup
            • EKS
              • Existing Application Load Balancer
              • Calculate Setup Cost for EKS Cluster
            • GCP
            • AKS
            • Self Managed
              • Microk8s with EKS-D
          • HyperTest Installation
      • Mirror Traffic
      • Configure HyperTest
      • Automate Starting a Test
        • CI Integration
          • GitHub Checks Integration
            • Mandatory checks
          • Gitlab Integration
          • Bitbucket Integration
          • Jenkins Pipeline
            • Jenkins Plugins for PR events
  • Upgrade HyperTest
    • Upgrade HyperTest
      • Linux VM
      • Kubernetes Cluster
  • User Guides
    • Usage Guide
      • Install and Configure HyperTest
        • Install HyperTest
        • Configure Base DNS
        • Add New Service
      • Tests Runs and Analysis
        • View Test Cases
        • Start New Test Run
        • Understand Your Test Run Analysis
        • Prioritize Your Error Types
        • Track Bugs
        • Ignore Errors/Desired Changes
        • View/Download Report
        • View Consolidated Dashboard Reports
        • Sign-off Reports
        • Reduce Execution Time
        • Deduplication Rules
      • Troubleshooting and FAQs
    • Best Practices Guide
      • Cost Optimization
    • Dashboard Tour
      • Dashboard
      • All Sessions
      • Regression Report
      • Notifications
      • First Test Run
      • Interactions
      • Custom Analysis
      • Configuration
    • User Management
      • Create Admin User
      • Roles, Groups & Users
      • Enabling User Signup
    • Other Guides
      • Basic Nginx Auth for Linux HT
  • Middleware
  • Advanced Features
    • Import test cases from Postman
  • Change Log
  • Troubleshooting
  • FAQs
    • Setup
    • General
    • Regression Report
  • Glossary
    • Session
Powered by GitBook
On this page
  • Types of Notification
  • Enabling Notifications
  1. User Guides
  2. Dashboard Tour

Notifications

PreviousRegression ReportNextFirst Test Run

Last updated 2 years ago

Notifications are messages delivered whenever some events happen within HyperTest. The Notifications section can be opened from the dashboard.

Types of Notification

There are four types of notifications, depending upon the type of event:

  • TEST_STARTED: Fired whenever a new test starts.

  • TEST_COMPLETED Fired whenever a test is completed.

  • NO_TRAFFIC_RECENTLY Fires a notification if HyperTest does not receive any traffic for an amount of time (hours) that is equal to NO_RECENT_TRAFFIC_THRESHOLD_HOURS as specified in the . On receiving of such a notification, it is advisable to confirm if the traffic mirroring works as intended in the

  • WEEKLY_REPORT Sends out weekly report on the day specified in the WEEKLY_REPORTS_DAY parameter in the config. The weekly report contains the cumulative result of the tests that it performed since the last day of weekly report.

Enabling Notifications

The notification dialog contains 3 fields:

  1. Description: Explains when the notification is sent

  2. E-Mails: List of recipient mails

  3. Webhook URL: A single url that acts as a webhook, receives the same notification message as email

It is not mandatory to provide both an email list and a webhook url

config
installation instructions