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
  • How to view Upstream Trace
  • Interservice Testing: Accepting Changes
  1. Impact Features

Inter Service Testing

PreviousDelete Recorded RequestsNextSlack Integration

Last updated 6 months ago

HyperTest, when integrated with all of your services, enables a developer to visualize their service mesh and service interactions.

This helps users in catching any inter-service breaks.

How to view Upstream Trace

Assume HyperTest is deployed in five services, microservice-app-1, microservice-app-2, microservice-app-3, microservice-app-4 and microservice-app-5. All of these services are interacting with each other.

These services have HyperTest running on them and recording traffic 24*7. Also, we have recorded requests and replayed them to check for any deviations.

  1. We will open the service, microservice-app-4 , open it's TEST RESULTS and open any of the test cases that are present.

  2. Click on up Upstream Trace.

  1. A chart pops up which shows how this current service is dependent on the other services. You can use the zoom option to visualize the depth inter-service interactions better.

  1. This shows which of these services upstream will be effected directly or indirectly if this service goes down.

Interservice Testing: Accepting Changes

In one of the previous sections, we discussed that the users can accept changes to confirm to HyperTest that this is a desired change so that we do not report this in future.

With upstream trace, users can visualize which service upstream will be directly affected if this change is accepted.

Once you click on Accept All Changes, a window pops up which warns the user that this mock is also utilized in a call upstream.

You can click on Show Upstream Trace to understand which service will get effected directly if this change is accepted.

Note: Accepting changes in your current mock will also update the mock in the service upstream.