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
  1. User Guides
  2. Usage Guide
  3. Tests Runs and Analysis

Prioritize Your Error Types

PreviousUnderstand Your Test Run AnalysisNextTrack Bugs

Last updated 2 years ago

This page contains list of errors which are captured by HyperTest alongwith their default severity level.

While you run a test, you can choose to capture only some error types (difference in responses) with custom severity levels such as only very high and high and ignore the medium and low severity errors

  • Go to service dashboard

  • Navigate to Settings from left panel

  • Navigate to Error Types

  • Click on customize to change the default severity level for a difference type

Difference Types

Error Types
  • CONTENT_TYPE_CHANGED: Change in the content type of response

  • STATUS_CODE_CHANGED: Change in the status code of the response

  • HEADER_REMOVED: Header Removed

  • HEADER_ADDED: Addition of header in the response

  • HEADER_MODIFIED: Modification of header in the response

  • KEY_REMOVED: Removal of a key-value pair in the response

  • KEY_ADDED: Addition of a key-value pair in the response

  • VALUE_MODIFIED: Modification of the value of a key in the response

  • ARRAY_ORDER_CHANGED: Change in the order of elements in the array in a response

  • ARRAY_ORDER_CHANGED_KEY_REMOVED: Removal of an element in an array in the response

  • ARRAY_ORDER_CHANGED_KEY_ADDED: Addition of element in an array in the response

  • ARRAY_ORDER_CHANGED_VALUE_MODIFIED: Modification of an element in an array in the response