Skip to content

216 — should test start date and due date from Sydney to London

Description

Cross-timezone check for a time record created in Sydney (Australia/Sydney) and viewed in London (Europe/London). Time records carry a real time-of-day, so this scenario verifies that the London viewer sees the same absolute moment expressed in London local time — both in the time-records list, the edit form, and the calendar tooltip.

Preconditions

  • Signed-in tenant with no existing time records.
  • Browser context is opened with timezoneId = Australia/Sydney for the author and later re-opened with timezoneId = Europe/London for the viewer.
  • The author lands on the dashboard.

Steps

  1. In the Sydney window, open Time Records, click Create Time Record and switch to the detailed view. Note the default start and end date+time as the test will assert on those exact values, then set a rate of 200.
  2. Expected: the form's Start Date, End Date, Start Time and End Time fields display the captured Sydney values.
  3. Click Create. Expected: the "Created" popup appears and row 0 of the time-records list shows the captured Sydney start/end date+time.
  4. Open the calendar, click the matching day. Expected: the event tooltip for this record shows the captured Sydney start/end date+time, duration "01:00" and billable "0%".
  5. Close the Sydney window and re-open the app in a fresh window with the London timezone.
  6. Open Time Records. Expected: row 0 shows the Sydney start/end date+time converted into London local time (typically the previous calendar day).
  7. Open the record. Expected: the form's Start Date, End Date, Start Time and End Time fields show the London-local equivalents of the original Sydney moments.
  8. Press Escape, open the calendar and click the matching day. Expected: the event tooltip for this record shows the London-converted start/end date+time, duration "01:00" and billable "0%".
  • Spec: playwright/tests/integration/dateTime.spec.ts (line 1540)