Case study

A timezone bug that double-booked a clinic's calendar

A timezone bug double-booked slots and overran the calendar. We corrected it across time zones and covered it with tests.

Clinic booking app · scheduling
double-booked slotscorrect across time zones · covered by tests

The challenge

A clinic's online booking app double-booked appointment slots and let bookings spill past the end of the day — a scheduling mess that fell on the front desk to untangle.

The context

Times were handled inconsistently between the browser, the server and the database, so the same slot meant different things depending on where it was read. It broke worst for users in a different timezone than the clinic.

What we did

  • Mapped where times were created, stored and displayed, and where the timezone was being lost.
  • Standardised on a single, unambiguous representation of time end to end.
  • Fixed the slot logic so overlaps and end-of-day overruns are impossible.
  • Covered the scheduling rules with tests across multiple time zones.

The outcome

Slots are correct regardless of the visitor's timezone, double-booking is designed out, and the scheduling rules are locked in by tests.

Stack
PlaywrightTypeScript
Get a free audit

Ship the next release without holding your breath.

Tell us what you're building — or what's breaking. We reply within one business day with a concrete plan, not a sales deck.

Or, the direct route
contact@qatestingplus.com
Replies from a human, not a CRM.

By sending this message, you agree to our Privacy Policy.