How It Works?
Last updated
Last updated
HyperTest operates in two modes: RECORD & REPLAY. The test case generation happens in RECORD mode and the Test Run is called the REPLAY.
There are 3 major components at play here:
SDK: Facilitates capturing incoming/outgoing traffic by instrumenting libraries thus generating test cases and mocks, also it provides appropriate mocks in REPLAY mode.
CLI: Runs Test by spinning up your app in isolation by injecting required mocks, replay's recorded traffic, and generates the report.
HyperTest Server: Serves the HyperTest Dashboard and stores all the test cases and results.
With HyperTest SDK integration in place, when a Client makes an API call to the UI Gateway Service it in turn makes some requests to external services to give a response.
All the outbound calls to the downstream services such as Redis or Catalog Services are being recorded by HyperTest SDK with their responses to be mocked during REPLAY. The Catalog service is also instrumented with the SDK it captures the Incoming Request from Gateway Service and records it as a test case with its mocks.
Whenever a Test is Initiated by HT CLI, it spawns a new process of the Application Under Test and supplies the mocks required for boot via SDK.
After successfully starting the App it starts running the same requests(Test Cases) with the mocks and generates a regression report which can be accessed by the Dashboard.
