Test reminder scheduling across dates and clock changes.

Instruction: Create a compact test matrix with exact expected UTC times, validation outcomes and display checks.

Context:

A fictional product schedules one-time reminders. A valid local date and time is converted using the user's selected zone and saved as a UTC instant. A nonexistent local time must be rejected. When a local time occurs twice, the user must choose an offset before saving. Changing display language must not change the instant. Use the following synthetic clock fixtures rather than assuming rules for a real region.

  • Ordinary case: October 20, 2026 at 09:00, offset UTC+02:00.
  • Date crossing: October 20, 2026 at 23:30, offset UTC−05:00.
  • Repeated time: October 20, 2026 at 01:30 occurs once at UTC−04:00 and again at UTC−05:00.
  • Missing time: on the synthetic jump date, the clock moves directly from 01:59:59 to 03:00:00; a user enters 02:30.

These transitions are controlled test inputs, not claims about an actual country's clock. The API returns a machine-readable UTC timestamp; the UI shows the selected local date, time and zone.

Updated

Official answer available

Read the opening below, then unlock the full answer and practical guidance.

I would compare the stored instant with an independently calculated UTC value, then check the local display after reopening the reminder. The ordinary 09:00 at UTC+02:00 case must store 07:00Z on October 20...

Upgrade to view official answer

Related Questions