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
      • CLI Login
      • Type References
      • 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
      • 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
    • 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
  • Why it happens?
  • Resolution
  1. Interpreting Test Results

Mock Not Found

PreviousUnderstanding Results CategoriesNextAI Match Mocks

Last updated 7 months ago

Mock not found or Outbound call not found means that an outbound call was made by the application in the Replay Mode, however, it was not recorded by HyperTest in record mode.

Why it happens?

This corresponds to a change in your code that HyperTest cannot mock in replay since it was not seen before. Consider this as a new change

This can be understood as a change in the behavior in the application which was not present during the record mode, however, has resurfaced in the replay mode.

Resolution

In case this behavior is expected, you can go ahead and click on 'Accept all changes' to validate this change.

Note: Accepting all changes for any test means that a user is forcefully making sure that the following test has passed. It will go straight to the 'passed' section of the test.