Inter Service Testing
Last updated
Last updated
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.
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.
We will open the service, microservice-app-4 , open it's TEST RESULTS and open any of the test cases that are present.
Click on up Upstream Trace.
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.
This shows which of these services upstream will be effected directly or indirectly if this service goes down.
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.
