Automate API Testing with Record and Replay
This is shailendra here. Founder at HyperTest - hypertest.co We are trying to make integration testing easy for developers. A lot of other teams and tools have taken a stab at this problem and having seen them we believe we have improvised the approach to help developers achieve this with minimum effort and pain. How it works: Developers set-up our SDK (2-lines) in the source code their (backend) services and configure it to record traffic from any environment. When HyperTest works in RECORD mode it collects end to end trace of every incoming request i.e. the request, response and outbound…
What it does
In the maker’s words, at launch
This is shailendra here. Founder at HyperTest - hypertest.co We are trying to make integration testing easy for developers. A lot of other teams and tools have taken a stab at this problem and having seen them we believe we have improvised the approach to help developers achieve this with minimum effort and pain. How it works: Developers set-up our SDK (2-lines) in the source code their (backend) services and configure it to record traffic from any environment. When HyperTest works in RECORD mode it collects end to end trace of every incoming request i.e. the request, response and outbound calls. These requests (tests) can be replayed on a new build later (pre-push or at CI) to check for regressions in API responses and outbound calls. In the REPLAY mode HyperTest uses mocked responses of all dependent systems to keep tests non-flakey and results deterministic and consistent. 3-min demo - https://www.youtube.com/watch?v=x6hmDUNFGW4 What does it do: HyperTest SDK auto-instruments all key functions and methods across all libraries you use to make outbound calls. This helps HyperTest mock these calls in REPLAY without asking developers to make any change in their source code. How is this better: 1. Set up is just like how you will set up an APM, i.e., 5 mins adding 2-lines of the SDK. 2. Support all protocols like http, graphQL, gRPC, Kafka and AMQP to cater to more use cases. Adding more as we speak 3. Test can be generated from any environment can be run anywhere even locally. 4. Active de-duplication to reduce the number of requests run on REPLAY. Optimise for code coverage & filter requests that don't cover additional lines of code 5. Distributed tracing to help developers debug root cause faster 6. Auto-updates mocks as dependencies change to keep test results trustworthy. HyperTest is currently available only for node projects. We work the teams with 5 or more services at the moment and have 50+ teams using it actively. If this seems valuable can set-up a quick intro and explain how to get started here -https://calendly.com/shailendra-hypertest/30min Would love feedback!
Does the same job
all alternatives →
More dev tools this month
the category →
Open-source GTM skills for technical founders
Dev tools · 29d ago · gtmcofounder.com
OpenTrailPaper is open-source bike computer firmware for the LilyGO T5S3 4.7" E-Paper PRO. It supports offline maps, GPX routes, FIT recording and Bluetooth sensors.
Dev tools · 1d ago · opentrailpaper.com
Launched alongside, September 2024
the whole month →
BeforeSunset AI 2.0▲1,267Personalized AI daily planning that suits your life
AI · 2024 · beforesunset.ai
