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

AI Match Mocks

PreviousMock Not FoundNextAccepting Changes

Last updated 7 months ago

When HyperTest AI finds an outbound call during the Replay mode that does not have an exact same outbound call in Record mode, it matches this call with one closest in schema to avoid Mock Not Found scenarios.

This is a best match scenario orchestrated by HyperTest's AI. It matches mocks of requests between record and replay with minimal difference in schema of the response as well as the outbound calls.

Let's try to understand this by taking an Example:

Suppose you've 2 APIs: createProduct and updateStock, and now you've introduced a new column to your stock table called "restockNeeded" whose value will be set on the count stock we have. When we recorded these 2 APIs we did not have that column, now in your new PR you've added it and you're trying to run a Test, you would see something like this:

Both the APIs have reported a change that a new Key has been added to the sequelize-mode-update mock.

This has been made possible by AI matches, here we looked at all the available recorded mocks and decided to pick a closest mock to the current input of the mock and reported this change.