QA Toolbox logoQA Toolbox
6 min readGuidesAPI testing

Unix Timestamps and Timezones: A Survival Guide for Testers

Date and time bugs are a QA classic because they hide in plain sight: the code works, the tests pass, and then a user in another timezone books an appointment for yesterday. If you can read timestamps fluently, you'll catch these in review instead of in production.

First, decode what you're looking at

APIs and databases are full of numbers like 1782518400. Paste one into the Unix Timestamp to Date and you get the human-readable moment in both UTC and your local time. Going the other way — building a request that needs "next Tuesday at 14:00" as an epoch value — the Date to Unix Timestamp does the conversion without you doing epoch math in your head.

Seconds vs milliseconds is the most common timestamp bug in the wild. A 10-digit value is seconds; 13 digits is milliseconds. Mix them up and dates land in 1970 or in the year 57,000 — if you see either in a UI, you already know the diagnosis.

The UTC discipline

The convention that keeps systems sane: store and transmit in UTC, convert at the edge for display. As a tester, that gives you two cheap checks on any feature that shows a time. Take the UTC value from the API response, run it through the UTC to Local Time converter, and confirm the UI shows exactly that. Then take what a user would type into a form, convert it with Local Time to UTC, and confirm that's what actually got stored. Any mismatch is a bug with a precise, reportable delta.

Timezone test cases worth writing

  • A user in a timezone ahead of UTC (e.g. Asia/Manila) and one behind (e.g. America/Los_Angeles) — date-boundary bugs only show up on one side.
  • An event scheduled across a DST transition — times shortly before and after the clocks change, in a zone that observes it.
  • Midnight-adjacent values — 23:59 local on the last day of a month is the classic "report shows the wrong month" trigger.
  • A half-hour offset zone like Asia/Kolkata (UTC+5:30) — code that assumes whole-hour offsets breaks here.

The Timezone Converter converts a moment between any two zones directly, which is exactly what you need when designing these cases or verifying "the meeting invite says 9:00 in Berlin — what should the New York attendee see?"

Developers hit the same wall from the other side — checking what a timestamp in a log means, or what value a scheduled job should fire at. Fluency in epoch-and-UTC is one of those skills that quietly speeds up everyone on the team.