Hypertest v2 Docs
HyperTest
  • Overview
    • How It Works?
  • SETUP GUIDE
    • Installation
      • Deploy HyperTest Server
      • Creating your first User
      • Adding your first service
      • Integrate SDK
        • Node.js
          • Node.js SDK with CJS
          • Node.js SDK with ESM
        • Java
    • Start a Test Run
      • Node
      • Java
    • Interpreting Test Results
      • Test Results
      • Understanding Results Categories
      • Mock Not Found
      • AI Match Mocks
      • Accepting Changes
  • USER GUIDES
    • Node.js SDK
      • Limit memory usage
      • Supported NPM packages
      • Mock Dependencies Manually
      • CLI Login
      • Unmocking/Passing Through
      • Sampling and blocking requests
      • Manage Global Variables
      • Mocking Environment Variables
      • Tags
      • Set HTTP path patterns
      • Discard a test case(Request) while recording
      • Set Git Commit Hash
      • Code coverage based features
        • Continuous Coverage
        • Updating test coverage
        • Running post test deduplication
        • Only testing modified requests
        • Ignore differences for unmodified requests
      • Experimental flags
      • Manual Request
      • Only testing modified requests
      • Server hooks
      • Update HT-CLI and Node-SDK
      • Type References
    • Java SDK
      • Sampling and blocking requests
      • Mock Dependencies Manually
      • Tags
      • Unmocking/Passing Through
      • Code Coverage Setup and Report Generation
      • Supported Java packages
    • Build your own Docker Image
    • CLI Config
    • Ignoring Differences
      • Type References for Filter functions
  • Impact Features
    • Fast Mode
    • Code Coverage Report
    • Delete Recorded Requests
    • Inter Service Testing
  • Release History
    • Slack Integration
    • Version History
Powered by GitBook
On this page
  1. SETUP GUIDE
  2. Interpreting Test Results

Test Results

PreviousInterpreting Test ResultsNextUnderstanding Results Categories

Last updated 7 months ago

Once you have run your test from CLI, you will be able to view the result from the dashboard itself. When you go to your service, it will be visible in 'Test Results'.

Types of Results

These results have been categorized in five different ways. These are:-

  • Total Requests: This is the list of all the requests run in a test.

  • Failed Requests: Requests with regressions in response or outbound calls.

  • Passed Requests: Requests with no regressions in response or outbound calls.

  • Mock Not Found: It means that an outbound call was made by the application in the Replay Mode, however, in record mode no such outbound call was seen by HT.

  • AI Matched Mocks: When HyperTest AI finds an outbound call during replay that does not have an exact same outbound call in Record, it matches it with one closest in schema to avoid Mock not founds.

You can open each one of these results and check for any regression or unusual behavior in your application.