> For the complete documentation index, see [llms.txt](https://docs-v2.hypertest.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-v2.hypertest.co/impact-features/inter-service-testing.md).

# Inter Service Testing

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

<figure><img src="https://lh7-rt.googleusercontent.com/slidesz/AGV_vUdjL5Ow-F3g9361HFAGsYltmAsasPWmFpaSt1nThcKdDHdZDiqplSIMgn4oiSbA7p5igda4xRR05w49L3qys2SAYs1vEbTrLqWiGVKlrpPw6XPB1q_S5JOa5m86FJlTJT2F0KayFl9nufetqdFBpTcW9yZXcSq_=s2048?key=P14UqOXts9F7iNY3Vy8xhg" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="/files/s1kQBLtRRjzUqiA2QFhi" alt=""><figcaption></figcaption></figure>

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.*

<figure><img src="/files/4V3XaBN01gxuzgIpkEC9" alt=""><figcaption></figcaption></figure>

3. 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.

<figure><img src="/files/zQ4Sx7O6Iuy0jM3k5auq" alt=""><figcaption></figcaption></figure>

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

## Interservice Testing: Accepting Changes&#x20;

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.&#x20;

With *upstream trace,* users can visualize which service upstream will be directly affected if this change is accepted.&#x20;

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.

<figure><img src="/files/1wTMgu7sjs3bY1Vec2Tc" alt=""><figcaption></figcaption></figure>

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

<figure><img src="/files/gfwmkRUqpxkUDQjf4zil" alt=""><figcaption></figcaption></figure>

**Note: Accepting changes in your current mock will also update the mock in the service upstream.**&#x20;