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
  • Kind of API failures HyperTest catches
  • Top Use Cases of HyperTest

HyperTest Overview

PreviousOthersNextIntroduction

Last updated 2 years ago

HyperTest is a no-code test automation tool that regresses all your APIs. It auto-generates end to end integration tests using your application's network traffic i.e. real user-activity.

Hence, eliminates the need to write or maintain any test suite for your backend or APIs.

HyperTest specialises in catching like data errors, contract failures or fatal crashes (response code errors) without asking teams to write, maintain or update any test scripts or test data.

Also reports i.e. slowness in APIs due to change in latency and bandwidth

Kind of API failures HyperTest catches

    • Response code errors like 400s, 500s

  1. Contract failures

    • Key_added

    • Data type_changed

  2. Data Errors

    • Increase in latency

    • Increase in Bandwidth

  • Discover and document all APIs

  • Catch Backward Incompatible API changes

  • Run Integration tests inside Github

  • Reproduce Failures inside Real User-Journey

  • Quantify Testing With Coverage

Fatal Crashes
Key_removed
Content type_changed
Value_modified
Slowness in APIs
See the entire list here
Top Use Cases of HyperTest
API performance issues
backward incompatible changes