Jabbar from Zoop shares how HyperTest cut post-merge bugs by 80% and improved interservice testing. 05 Min Read 21 February 2025 Zoop.one’s Success Story with HyperTest | Featuring Jabbar Vaishali Rastogi Ushnanshu Pant WhatsApp LinkedIn X (Twitter) Copy link Hi everyone, this is Ushnanshu Pant , Customer Solution Expert at HyperTest. I recently had the pleasure of speaking with Jabbar , who works as an SDE-3 at Zoop.one —a B2B product company specializing in KYC solutions and customer onboarding . We talked about the key testing challenges they faced, how HyperTest transformed their approach, and the tangible impact it has had on their development process. Let’s dive in! 1️⃣ What were the primary challenges you faced in testing before implementing HyperTest? Jabbar: I would like to note down the one is like main challenges like mocking the 3rd party API calls, the database query and the Kafka queue messages. And the second challenge was interservice dependency, like if one service is dependent on the other, we need the mockup or the services whether the services are working fine or not. This was lacking and we got this solved after we implemented HyperTest. 👉 It sounds like dependency management and real-time validation were major roadblocks. 2️⃣ How did HyperTest help address these challenges? Jabbar: Initially, we were just mocking third-party libraries. One potential challenge was detecting dependencies between services—for example, if Service A had some code changes that would affect Service B. Before HyperTest, we were setting up mocks for Service A's responses based on Service B, but we weren’t able to identify whether it would actually pass or fail in production. This interdependency issue, along with memory leaks, was a major concern that HyperTest helped resolve effectively. 👉 So, HyperTest not only streamlined the mocking process but also improved visibility into real production behavior. 3️⃣ Can you share some specific features of HyperTest that you found most beneficial? Jabbar: Certainly, one of the standout features is being able to derive test results directly from actual traffic, which means we can simulate real customer interactions without setups. This was a huge advantage because it also allowed us to predict resource needs like CPU or memory scaling for production. Another important feature was automating third-party API interactions, which eliminated the need to write extra code for these operations. 👉 That’s great! Being able to simulate production traffic and automate dependencies must have streamlined your workflow. 4️⃣ What improvements have you noticed in your development and QA processes after integrating HyperTest? Jabbar: With HyperTest, we've seen a dramatic reduction in bugs in our production environment. Before its integration, we identified 40 to 50% issues post-merge to production. Now, it’s less than 10%. This efficiency not only saves time but also significantly reduces the error rate, which I believe is currently around 7 to 8%. The QA team doesn’t have to wait around anymore; they can instantly check the reports, verify API performance, and highlight any necessary changes. This streamlined process has eased the workload considerably for our team. 👉 That’s a huge drop in post-merge issues! 5️⃣ How has HyperTest transformed the dynamics between developers and the QA team? Jabbar: HyperTest acts like a 'ship rocket' between developers and QA, boosting both efficiency and morale. It minimizes conflicts by clearly delineating responsibilities, which in turn reduces friction and misunderstandings. 👉 That’s a great analogy! When teams spend less time debating bugs and more time building, it’s a win for everyone. 6️⃣ What about the coverage reports provided by HyperTest? How effective are they? Jabbar: The coverage reports from HyperTest are thorough, providing insights into line, branch, and state coverage, among others. These reports help our developers ensure no critical areas are missed, covering edges that might typically be overlooked. It was fantastic catching up with Jabbar and hearing how HyperTest has streamlined testing, improved collaboration, and significantly reduced post-production issues at Zoop.one . Their experience really highlights how the right tools can make all the difference in modern software development. A big thank you to Jabbar for sharing these insights! If you're facing similar testing challenges, feel free to reach out —we’d love to help. 🚀 Prevent Logical bugs in your databases calls, queues and external APIs or services Take a Live Tour Book a Demo

Get actionable strategies for end-to-end integration testing with industry expert Sidharth. Find out how to run tests from any environment and enhance product quality early in development. Best Practices 58 min. Build E2E Integration Tests Without Managing Test Environments or Test Data Get actionable strategies for end-to-end integration testing with industry expert Sidharth. Find out how to run tests from any environment and enhance product quality early in development. Get Access Speakers Sidharth Shukla SDE 2 | 60K followers on Linkedin Amazon Shailendra Singh Founder HyperTest Prevent Logical bugs in your database calls, queues and external APIs or services Book a Demo

Learn from system design expert Raul Junco as he walks through automating API, message queue, and database mocking with HyperTest for efficient testing. Mocking 60 min. Mock APIs Message Queues and Databases in One Place Learn from system design expert Raul Junco as he walks through automating API, message queue, and database mocking with HyperTest for efficient testing. Get Access Speakers Shailendra Singh Founder HyperTest Raul Junco Software Engineering Manager ANDMORE Prevent Logical bugs in your database calls, queues and external APIs or services Book a Demo

We're joining the GenAI wave!. While GenAI has been a game-changer in many sectors, we believe there's room for improvement in software testing. GenAI for Testing 44 min. What no one will tell you about using GenAI for Testing We're joining the GenAI wave!. While GenAI has been a game-changer in many sectors, we believe there's room for improvement in software testing. Get Access Speakers Shailendra Singh Founder HyperTest Karan Raina Co-Founder, CTO HyperTest Prevent Logical bugs in your database calls, queues and external APIs or services Book a Demo

Fyers wanted a solution to automatically detect and report regressions such as content_type_change, schema_failure, and key_removed at scale from the outset. This would streamline fixing them before they became critical issues. Customer Success Half a Million Users, Zero Schema Failures: How Fyers Leverages Hypertest Fyers wanted a solution to automatically detect and report regressions such as content_type_change, schema_failure, and key_removed at scale from the outset. This would streamline fixing them before they became critical issues. Pain Points: Slow automation hampered Fyers' rapid development cycles. Bugs snuck through testing, disrupting releases and costing money. Existing frameworks couldn't handle complex scenarios, leading to production issues. Results: Regression testing slashed from days to 3 hours. Automated test coverage soared to 85%. Faster feedback loops sped up bug resolution before release. About: Founded: 2015 Employees: 300 Industry: Stockbroking and Investment Services Clients: 500,000+ investors across NSE, BSE, and MCX Fyers, established in 2015, has been dedicated to transforming trading and investment in India. As a dynamic startup in stockbroking, Fyers supports seamless trading for over half a million investors on major Indian exchanges. From its early days with 1,000 accounts in 2016, Fyers has grown to a formidable force with a strong team of 300 and a consistent month-on-month growth rate of 15%. Fyer’s Requirements: Enhance code management control by 30% to streamline workflows and deployments. Refine automation processes to achieve performance efficiency. Increase code coverage by at least 40% to substantially reduce production defects. Challenge: In the high-stakes fintech sector, where daily transactions exceed 2 billion USD, the reliability of Fyers' technology platforms is paramount. The rapid pace of trading demands equally swift technological responses. Fyers’ technology stack included over 100+ microservices, which were initially supported by an in-house automation framework that struggled to match the speed of transactions. The need to enhance release velocity was critical; however, the existing framework was not only slowing down releases but also failing to capture bugs effectively. The framework’s inability to handle complex edge cases resulted in production issues that were costly both in terms of time and financial resources. Solution: After evaluating various tools and realizing the limitations in documentation, user experience, and support, Fyers chose HyperTest for its integration testing capabilities. HyperTest drastically reduced the regression testing time to under 3 hours, down from 3-4 days. The tool enabled rapid feedback to developers, facilitating quick bug fixes and smooth rollouts of new updates, which was crucial for high release velocity . HyperTest eliminated the labor-intensive process of manual test writing by automatically generating test cases for all critical user flows . This capability saved critical dev time spent on test maintenance increasing overall test coverage to 85% autonomously. HyperTest ensured critical regressions like schema failures or data changes were never missed during testing. The best thing about HyperTest is that you don't need to write and maintain any unit tests. Also any enhancements or additions to the APIs can be quickly tested, ensuring it is backwards compatible. So this makes sure of bug-free deployments. The UI is very easy to use. - Khyati Suthar, Software Developer Read it now How Yellow.ai Employs HyperTest to Achieve 95% API Coverage and Ensure a Flawless Production Environment Read it now Processing 1.5 Million Orders, Zero Downtime: How Nykaa Optimizes with HyperTest View all Customers Catch regressions in code, databases calls, queues and external APIs or services Take a Live Tour Book a Demo

Incomplete code coverage in Cashify's testing was leaving bugs undetected into their production. They wanted a solution that could give them more code coverage and better release cycles to help identify and fix these issues faster, ensuring a more reliable platform. Customer Success How Cashify Achieved Over 90% Code Coverage in Days with HyperTest Incomplete code coverage in Cashify's testing was leaving bugs undetected into their production. They wanted a solution that could give them more code coverage and better release cycles to help identify and fix these issues faster, ensuring a more reliable platform. Pain Points: Incomplete testing exposed critical production flaws Slow API testing slowed innovation and market response Buggy tools missed critical issues, impacting customer experience Results: Boosted code coverage (90%) slashed production risks Streamlined API testing cut time in half Higher code quality led to 84% fewer production bugs About: Founded: 2013 Employees: 800+ Industry: E-commerce for used electronics Users: 2 million+ Cashify is a pioneering online marketplace in India specializing in the resale of used electronic gadgets. With a robust online platform and physical kiosks, Cashify enables over two million users across 1,500 cities to effortlessly sell and buy used smartphones, tablets, laptops, and more. Emphasizing sustainability, Cashify provides instant cash for old devices along with convenient home pick-up services. Having a significant focus on smartphones, which constitute 90% of its business, Cashify continues to expand its services and technology under the guidance of its founder and CEO, Mandeep Manocha, and a dedicated engineering team of over 200 employees. Cashify's Requirements: Substantial enhancement of code coverage across 100+ micro-services to minimize production defects. Streamline and optimize automation processes to increase efficiency and reliability in API testing. Implement robust testing solutions that integrate seamlessly with existing CI pipelines and require minimal maintenance. Challenge: Cashify, a leader in the resale of electronic gadgets, managed a complex technology stack that included over 100 services and APIs. Previously relying on semi-automated tools like RestAssured and Postman, Cashify faced challenges with these tools' ability to provide adequate test coverage and speed, leading to operational inefficiencies and vulnerabilities. Critical bugs frequently slipped through tests, leading to financial discrepancies and user dissatisfaction. Manual testing processes were slow and often missed capturing bugs in timely updates, causing delays in deployment. Previous tools provided insufficient coverage, allowing vulnerabilities to persist and disrupt operations. Solution: To tackle these challenges, Cashify implemented HyperTest, a cutting-edge automation tool designed to enhance testing capabilities without the need for extensive manual intervention. By integrating HyperTest into their CI pipeline, Cashify achieved comprehensive and automated code coverage of up to 95%, drastically reducing the incidence of critical bugs reaching production environments. The tool facilitated rapid and efficient API testing, cutting down the testing duration significantly, which allowed for quicker feedback and iterations. HyperTest's no-code regression testing capabilities enabled Cashify to automatically generate and run tests based on real user interactions, ensuring that new updates were thoroughly vetted before deployment. This approach not only improved operational efficiency but also enhanced the reliability and security of the Cashify platform. HyperTest is able to detect a lot of issues missed by our current automated testing suite. The biggest reason I signed up with HyperTest was when it was able to detect a critical issue in our application that our current suites completely missed". In addition to zero maintenance, Cashify now triggers tests from their CI pipeline, neatly integrating into their release process. - Pankaj Kumar Aggarwal, VP of Engineering Read it now How Yellow.ai Employs HyperTest to Achieve 95% API Coverage and Ensure a Flawless Production Environment Read it now Processing 1.5 Million Orders, Zero Downtime: How Nykaa Optimizes with HyperTest View all Customers Catch regressions in code, databases calls, queues and external APIs or services Take a Live Tour Book a Demo

HyperTest Way To Implement Shift-Left Testing Download now Prevent Logical bugs in your database calls, queues and external APIs or services Book a Demo

A Guide to the Top 5 Katalon Alternatives Download now Prevent Logical bugs in your database calls, queues and external APIs or services Book a Demo

Nykaa wanted to improve how well their app is tested by adding more test case scenarios that closely simulate real-world usage. This way, they can quickly find and fix issues, aiming for a improved customer experience. Customer Success Processing 1.5 Million Orders, Zero Downtime: How Nykaa Optimizes with HyperTest Nykaa wanted to improve how well their app is tested by adding more test case scenarios that closely simulate real-world usage. This way, they can quickly find and fix issues, aiming for a improved customer experience. Pain Points: Inefficient automation introduced defects into the production environment. Extended release cycles constrained timely deployments. Insufficient code coverage resulted in undetected vulnerabilities. Results: Achieved 90% reduction in regression testing time. Improved release velocity by 2x. 90% lesser integration defects or incidents in production. About: Founded: 2012 Employees: 4168+ Industry: Beauty and Fashion E-commerce Users: 17 million+ Nykaa is India's premier lifestyle and fashion retail destination, providing a comprehensive array of products across cosmetics, skincare, haircare, fragrances, personal care, and wellness categories for both women and men. Nykaa made an impressive stock market debut, reaching a valuation of over $13 billion. The company's shares initially listed at an 82% premium and have climbed to approximately 96%. Listed on the BSE since November 2021, Nykaa now boasts a market capitalization of $8.3 billion, underlining its significant impact and strategic presence in the beauty and lifestyle market. Nykaa's Requirements: High fidelity integration testing for a service oriented architecture. Refined automation processes to deliver tangible outcomes. Improved code coverage to minimize production defects. Challenge: Operating a dynamic e-commerce platform with daily orders exceeding 70,000, Nykaa recognized the need for a sophisticated testing approach suitable for their rapidly growing microservices. They had implemented an automation suite to safeguard their revenue and prevent defects from reaching production. Despite the deployment of a new automated system, occasional defects still appeared production. Initial automation efforts were inadequate, not fully preventing defects and causing the team to shift focus toward managing disruptive changes linked to microservice expansion. Integration testing was excessively time-consuming, with many defects originating from backend systems, affecting release velocity and product quality. Low code coverage in earlier stages meant that many potential issues went undetected until later in the development cycle, increasing risk and remediation costs. Solution: Nykaa adopted HyperTest to enhance automation and effectively test their services expansion , aiming to prevent potential disruptions. This solution streamlined their feature release process, allowing for comprehensive testing without separate test setups. HyperTest facilitated rapid integration testing for microservices, reducing the testing time from several days to mere minutes—a 70% increase in testing efficiency. This transformation boosted speed of feature releases by substantially shortened testing times. Additionally, with HyperTest, Nykaa achieved up to 90% code coverage, drastically reducing the incidence of critical bugs and vulnerabilities reaching the production environment. I have been using Hypertest for the past 2.5 years. It has made the QA cycle reliable providing the best quality, reducing a lot of manual effort, and thus saving functional bandwidth. The bugs which can be missed in automation can be easily caught with Hypertest. -Atul Arora, SDET Lead, Nykaa Read it now How Yellow.ai Employs HyperTest to Achieve 95% API Coverage and Ensure a Flawless Production Environment Read it now Airmeet and HyperTest: A Partnership to Erase 70% Outdated Mocks and Enhance Testing Speed By 80% View all Customers Catch regressions in code, databases calls, queues and external APIs or services Take a Live Tour Book a Demo

Learn how to streamline end-to-end testing by eliminating the need for test data preparation in our insightful webinar. E2E Testing 40 min. How to do End-to-End testing without preparing test data? Learn how to streamline end-to-end testing by eliminating the need for test data preparation in our insightful webinar. Get Access Speakers Shailendra Singh Founder HyperTest Karan Raina Co-Founder, CTO HyperTest Prevent Logical bugs in your database calls, queues and external APIs or services Book a Demo

Designed for software engineering leaders, Learn proven strategies to tackle challenges like missed deadlines, technical debt, and talent management. Best Practices 58 min. Ways to tackle Engineering Problems of High Growth Teams Designed for software engineering leaders, Learn proven strategies to tackle challenges like missed deadlines, technical debt, and talent management. Get Access Speakers Sancheeta Kaushal Head of Cloud Bolt.Earth Kanika Pandey Co-Founder, VP of Sales HyperTest Prevent Logical bugs in your database calls, queues and external APIs or services Book a Demo

Get all your HyperTest-related questions answered and unlock the power of automated testing for flawless microservices. Get to Know HyperTest Category Contribution Error Handling General Integration Mock Verification Mocking Setup Test Execution Test Maintenance Test Results Testing Troubleshooting Usage Use Cases Clear all How can I contribute to the development of HyperTest? At the moment, HyperTest is a closed-source project. However, we welcome your feature requests! Simply submit them to our support team, and we'll do our best to accommodate them in future updates. Is there support for versioning of API mocks to align with API version changes? Currently, HyperTest treats APIs with different versions as unique entities, without grouping them for version control. This means there's no specific provision to manage versioning of API mocks to align with API version changes. How to use HyperTest for load testing by simulating high volume of outbound calls? HyperTest is not designed specifically for load testing, other popular solutions specialize in this area. You might consider exploring tools like Apache JMeter, Gatling, LoadRunner, K6, or Locust for conducting load testing effectively. These tools offer robust features specifically tailored for load testing scenarios. Can HyperTest handle mocks for authenticated API calls? Indeed! HyperTest manages authenticated API calls by capturing the headers containing the authentication token. To address token expiry, we've customized the behavior of the jsonwebtoken library by patching it on runtime so that it doesn't throw errors when encountering expired tokens. This ensures that your authenticated routes remain valid at all times. What should I do if I see ‘Mock not found’? There are two scenarios in which you could encounter this issue: 1. You’ve added a new outbound call to your existing API and we haven’t captured that mock. In this case, you should re-record a new API interaction that has this outbound mock and delete the older one. 2. HyperTest was not able to identify the mock properly from the available mocks for the test. In this case, you should reach out to the support team to raise this issue. How can I request features or report bugs for HyperTest? You can reach out to our support team via email [[ INSERT_EMAIL_ID ]]. What are the common issues to look out for when using HyperTest? App crashes after integrating HyperTest SDK: There could be several reasons for App crashes, lets discuss one by one: 1. Incorrect configuration: Please make sure you provide the right configure while intializing HyperTest SDK, e.g., serviceId & apiKey. 2. Using unsupported version of programming language or Run time environments: As of now HyperTest supports Node.js versions >= v14. 3. Your application depends on some 3rd party service to provide boot configuration: If you're calling an external service to fetch boot configurations then it could cause issues as we would try to mock all the external calls and not having relevant config at boot during a test run might cause unexpected issues. To solve this you should put this call inside an unmocked context so that the call goes through all the time, you can find more about it here. 4. Unknown error originating from your dependency: If you're getting this error only when running you app with HyperTest SDK in place then it is possible that we have instrumented this dependency and it has some bug which is causing this error, in such case please report this issue to our support team and we will try to resolve it as soon as possible. 5. Cannot start server because port is not available: HyperTest internally spins up two servers and they listen on available ports of these ranges: SDK server: 3001-3010 and CLI server: 4001-4010. You can verify if your application is using the same port as one of these server by passing this env variable to HyperTest CLI: "DEBUG=ht*", this will log the ports being used. If found same port is being used then please change port of your end to solve this. Seeing MOCK_NOT_FOUND during test runs: There are two scenarios in which you could encounter this issue: 1. You’ve added a new outbound call to your existing API and we haven’t captured that mock. In this case, you should re-record a new API interaction that has this outbound mock and delete the older one. 2. HyperTest was not able to identify the mock properly from the available mocks for the test. In this case, you should reach out to the support team to raise this issue. Requests not getting captured: There could be several reasons for this, lets discuss one by one: 1. Use of incorrect serviceId: Please make sure you've copied the correct serviceId from the dashboard and you're viewing requests of that service only. 2. Initializing SDK before everything else: HyperTest works by monkey patching your dependencies, it is mandated that you initialize hypertest before doing anything in your entry file so that it patches all the dependencies before being used, if we dont do this then you might see missing mocks or requests. 3. Issue with Opentelemetery Trace Exporter: To debug further you can try setting env variable "DEBUG=ht*" to see debug logs by HyperTest SDK. If you see any log that starts with: "HT-ERROR: Failed to export traces:" then it's an issue from our end. In this case, you should reach out to the support team to raise this issue. Seeing exceptions in CLI test results: If you're seeing that exception count is more than 0 then you should look at the logs for app crashes and you will see the id of the test case under question, you can view the particular test case on the dashboard and figure out why it is crashing the app. If it's a stale request that doesn't resonate with the current state of your application then you can discard it. If this exception is unexplainable and you don't find a test case id in the logs then you can try turning on the debug logs for the CLI by setting this env variable "DEBUG=ht*" to see the detailed logs. No mocks for expected outbound calls: Usually, this means that we have not provided support for this dependency or there's a bug in the HyperTest instrumentation, in any case, please reach out to the support team to raise this issue. Where can I find logs or error messages generated by HyperTest? You will see HyperTest SDK logs in your Applications “stderr” output for enhanced debugging you can turn on debug logs by setting this environment variable “DEBUG: ht*”. How do I update or remove outdated mocks? You can accept changes found in the test report to update the mock, if they are not being used then accepting changes will remove that mock from the test, but you cannot manually update it. If a test seems outdated, you can record a new one and delete the old one from the dashboard. What should I do if HyperTest is not capturing certain outbound calls? First, verify if the dependency responsible for the outbound call is supported by HyperTest (check here). If it is, there may be a bug, and you should contact our team for assistance. If it's not supported, please submit a request to our team for adding support for that specific dependency. We'll prioritize adding support as soon as possible. Does HyperTest support distributed tracing for complex microservices interactions? HyperTest doesn't offer distributed tracing, meaning it doesn't capture all traces it receives. However, it does keep a record of unique server requests (test cases) and tracks the flow of interactions between different microservices. While this specific feature isn't available yet, it's planned for future implementation. Is HyperTest compatible with microservices architectures? Absolutely! HyperTest seamlessly integrates with microservices architectures. Developers can easily visualize their service mesh and the interactions between services. Plus, they'll receive alerts about any new changes made to upstream or downstream service contracts. Although this feature isn't currently available, it's on the roadmap and will be implemented soon.