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.

Best Practices for Performing Software Testing Download now Prevent Logical bugs in your database calls, queues and external APIs or services Book a Demo

How Effective API Testing Saved a Leading E-commerce Brand Download now Prevent Logical bugs in your database calls, queues and external APIs or services Book a Demo

Manual and Automated Testing Compared-Which Is Right for You Download now Prevent Logical bugs in your database calls, queues and external APIs or services 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. Prevent Logical bugs in your database calls, queues and external APIs or services Book a Demo

A comparison guide between Unit Integration and e2e tests Download now Prevent Logical bugs in your database calls, queues and external APIs or services Book a Demo

Testing runs parallel to development, allowing quick testing of small changes for immediate release. Ship Features 10x Faster with Shift-Left Testing Testing runs parallel to development, allowing quick testing of small changes for immediate release. Download now Prevent Logical bugs in your database calls, queues and external APIs or services Book a Demo