Skip to content

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

Description

Cross-timezone check for a time record created in London (Europe/London) and viewed in Sydney (Australia/Sydney). Time records carry a real time-of-day, so this scenario verifies that the Sydney viewer sees the same absolute moment expressed in Sydney 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 = Europe/London for the author and later re-opened with timezoneId = Australia/Sydney for the viewer.
  • The author lands on the dashboard.

Steps

  1. In the London 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 London values.
  3. Click Create. Expected: the "Created" popup appears and row 0 of the time-records list shows the captured London start/end date+time.
  4. Open the calendar, click the matching day. Expected: the event tooltip for this record shows the captured London start/end date+time, duration "01:00" and billable "0%".
  5. Close the London window and re-open the app in a fresh window with the Sydney timezone.
  6. Open Time Records. Expected: row 0 shows the London start/end date+time converted into Sydney local time (typically the next calendar day).
  7. Open the record. Expected: the form's Start Date, End Date, Start Time and End Time fields show the Sydney-local equivalents of the original London moments.
  8. Press Escape, open the calendar and click the matching day. Expected: the event tooltip for this record shows the Sydney-converted start/end date+time, duration "01:00" and billable "0%".
  • Spec: playwright/tests/integration/dateTime.spec.ts (line 1334)