The Largest Restaurant SAAS Company In India and Sea Improved Dev Productivity by 33% With HyperTest



LimeTray, based out of India, is one of the largest CRM solutions for restaurants chains across India and SEA. Currently used by 4000+ customers in 10+ countries, it sees 15.4M unique hits on their systems with 4.9M orders processed every month. The cloud SaaS helps small to large food outlets run their business online helping with new user acquisition, order management, inventory control, and much more.


With HyperTest, they have taken a more streamlined and automated approach to manage their product lifecycle, reduce downtime and optimize their QA resources.



The Challenge

“Selenium-based tests were not able to give us either speed or coverage”

The team struggled with issues common to frameworks like Selenium. QA teams spent a very long time creating tests and equally long managing them. Selenium written tests needed constant updates with application changes. Managing test data to create these tests was another big issue.

The dev teams felt that the QA team took inordinately long to green-lit releases. Bugs were reported post-release and reproduction was inadequate. This made Devs spend a lot of time fixing bugs of previous sprints and very little time on new feature development.

  • LONG RELEASE CYCLES

  • HIGH QA TIME IN SPRINTS

  • 1-2 DAYS TIME TO CODE PER TEST ON SELENIUM

  • TEST MAINTENANCE OF BRITTLE/FLAKEY TESTS

  • MANAGEMENT OF TEST DATA

  • POOR COVERAGE OF SELENIUM TESTS

The release cycle before HyperTest…

The current sprint size was 20 days i.e. 4 weeks. The team was spending close to 6-8 days doing just Quality Assurance.

Bad releases contributed to more than 80% of all big crashes and downtimes. The current QA strategy based on Selenium tests did little to prevent them.

The Dev teams spent a lot of time fixing bugs from the previous sprint because more than 50% of the failures were reported post-release. As a result, less than a third of the sprint time was actually used for any new development.

Moreover, bug reproduction was a tedious process that required a lot of coordination between Devs and QAs.



The Solution

HyperTest integrates on prod or any pre-prod environment of the client

HyperTest was set up in under 5 minutes in their staging environment. The biggest difference that HyperTest brought along with its ability to auto-generate tests was to let both Dev and QA teams detect and fix failures before new releases. It monitored the running application to create test data, and tests with better coverage than Selenium at one-tenth the cost. Though HyperTest was integrated into the staging, it was also run locally by the Dev team to quickly check for imminent failures even before the candidate was merged to staging.

With HyperTest, QAs can not just report but also reproduce the failure with a simple GUI that covers the entire error user journey. The client integrated HyperTest to their CI/CD pipeline triggering new tests for every new commit. This made failure feedback on new changes instant and detailed. New changes were also green-lit faster bringing down overall QA oversight. HyperTest created tests also helped identify which kind of users could be affected through parameters like location, device, browser, plan type, etc. Subsequently, debugging became faster for feature-flag based development.



Results


3 views0 comments