Travelchapter
- Year
- 2024-2025
- Role
- Software Engineer in Test (SEIT)
- Stack
- Cypress
- Gherkin
- JavaScript
- TypeScript
The problem
Two companies had recently merged, and the business needed confidence that consolidating their codebases wouldn't break existing functionality on either flagship site.
The approach
Built a Cypress test suite covering both flagship sites, verifying UI behaviour and confirming that the correct API calls fired for key user actions. Suites weren't just written: each one had to be confirmed working before it was allowed into the release pipeline, a gate rather than a formality.
The legacy gap
Some newly merged listings weren't returning valid room and bathroom counts, caused by discrepancies between the two legacy systems. The diagnosis itself wasn't the hard part once the pattern was visible. Fixing it at the source was on the table but out of scope for the time available on the engagement, so the choice was a workaround: a weekly script against the property catalogue that pinpointed exactly which listings were affected. It was built for handoff: a structured schema returning property name, ID and the missing attributes, landing before the first login each Monday, so business operations could find and fix the affected properties without an engineer in the loop.
The outcome
Documentation handed to the development team proved itself in use: one developer used it to extend the suite with a new mock test. He rolled off the engagement once the merge had stabilised, so whether the weekly script is still running isn't something he can confirm from here: the discrepancy it was built to catch may since have been fixed at the source, which would make the script redundant by design rather than failure.