The regression that used to eat days now runs itself, so a travel platform ships several times a week

The client is a modern travel platform where advisors book the trips and suppliers pay the commission — so the product is the business. DesiCrew runs the QA behind it: the test writing, the regression, and the automation that keeps releases moving without breaking what already works.

The platform ships constantly, several releases a week, and every release can break something that worked yesterday. A booking that fails, a commission that comes out wrong, a page that will not load on a phone — the traveller feels it first, and so does the advisor who loses the sale. The company builds the product. DesiCrew makes sure each release ships without taking the last one down with it.

01 — The Mandate

Advisors use the platform to book hotels, flights, transfers, tours, and everything else a trip needs. As the release pace climbed, the client needed a partner that could write the tests, run them, and automate them. DesiCrew runs that with a team of nine, and has for about a year and a half.

Coverage. Every release ticket and every regression pass comes through DesiCrew. Three lines of work. Writing the test cases, running functional and regression testing, and automating the suite. Always on. Regression five days a week, timed to the platform's release schedule.

02 — The Challenge

A travel platform that books real money is unforgiving. A booking that fails, a commission that comes out wrong, a flow that breaks on a phone — the advisor loses the sale while the traveller loses the trip. It has to be caught fast, because the releases do not slow down.

The releases never stop. Regression has to run five days a week against a product that keeps changing; testing it by hand either slows the releases down or starts to miss things. The target keeps moving. Requirements shift module to module as the platform learns what its advisors need, so the tests have to change as fast as the product does. It all connects to something else. The platform runs on third-party integrations for flights, hotels, and payments, where a break is not the platform's own code but is still the client's problem.

Anatomy of one bug that ships — why catching it early is the whole game

A bug caught in testing is a line in a report. The same bug in production is a failed booking, a support ticket, an advisor who did not get paid, and an engineer pulled off the next release to fix it. The cheapest place to catch it is before it ships.

03 — The Approach

DesiCrew built the coverage first, then automated the part that runs again and again.

A test plan built around the release schedule. Coverage for both the daily release tickets and the regression passes, so shipping fast does not mean shipping fragile. Full coverage, tracked in one place. DesiCrew wrote 4,056 test cases for the whole application and moved it onto Zephyr Scale, so test execution and defects are tracked together instead of scattered. Critical functionality first. The work went after the flows that would hurt most if they broke, and caught the critical defects that would have held up a release. Automated with Playwright. The slow, repetitive regression work was automated — 370 test cases now run themselves and keep pace with every release, cutting manual regression effort by around 80%. Across the engagement: 672 manual regression cycles and 1,603 automated ones.

04 — The Outcome

Clean builds, every release. Each release is tested with regression run against it first — so the platform ships at the pace it wants without the quality dropping.

Fewer bugs reach the people who matter. 5,413 defects caught before release, 467 of them major or critical — so a booking goes through, and the advisor gets paid. Time back for the core business. With QA owned end to end, the client's own people stay on the product and the advisors — building instead of firefighting release tickets.

05 — Why the relationship holds

DesiCrew did not just run the platform's testing. It built something the client keeps: the automated suite catches a regression the moment it appears, on every release, without anyone re-running it by hand.

That is why the work sits where it does. The client moved its test management onto the tool DesiCrew recommended and handed over the regression and automation its releases depend on. The suite is now part of how the platform ships, not a service running alongside it.

About DesiCrew

DesiCrew is an applied-intelligence company — the human and technology layer that makes AI systems and enterprise operations work reliably and grow at scale, refined in production since 2007. IIT Madras incubated · Everest Group PEAK Matrix 2024 · Great Place to Work.