timezone-mock

What is timezone-mock?

The 'timezone-mock' npm package allows developers to mock the system timezone in their Node.js applications. This is particularly useful for testing code that is sensitive to timezones without having to change the system timezone.

What are timezone-mock's main functionalities?

Mocking the System Timezone

This feature allows you to set a specific timezone for your Node.js application. The code sample demonstrates how to register the 'US/Pacific' timezone and then log the current date and time in that timezone.

const timezoneMock = require('timezone-mock');
timezoneMock.register('US/Pacific');
console.log(new Date().toString()); // Outputs date in US/Pacific timezone

Unregistering the Mocked Timezone

This feature allows you to unregister the mocked timezone and revert back to the system's default timezone. The code sample demonstrates how to unregister the 'US/Pacific' timezone and log the current date and time in the system's default timezone.

const timezoneMock = require('timezone-mock');
timezoneMock.register('US/Pacific');
console.log(new Date().toString()); // Outputs date in US/Pacific timezone
timezoneMock.unregister();
console.log(new Date().toString()); // Outputs date in the system's default timezone

Other packages similar to timezone-mock

mockdate

The 'mockdate' package allows you to mock the current date and time in your Node.js applications. Unlike 'timezone-mock', which focuses on timezones, 'mockdate' is more about setting a specific date and time for testing purposes.

sinon

The 'sinon' package is a comprehensive library for creating spies, stubs, and mocks in JavaScript. While it is not specifically focused on timezones, it can be used to mock dates and times, among other functionalities. It is more versatile but also more complex compared to 'timezone-mock'.

README

timezone-mock

A JavaScript library to mock the local timezone.

This module is useful for testing that code works correctly when run in other timezones, especially those which have Daily Saving Time if the timezone of your test system does not.

When register is called, it replaces the global Date constructor with a mocked Date object which behaves as if it is in the specified timezone.

Usage Example

var assert = require('assert');
var timezone_mock = require('timezone-mock');

function buggyCode() {
  // This function is potentially a bug since it's interpreting a string in
  // the local timezone, which will behave differently depending on which
  // system it is ran on.
  return new Date('2015-01-01 12:00:00').getTime();
}
var result_local = buggyCode();
timezone_mock.register('US/Pacific');
var result_pacific = buggyCode();
timezone_mock.register('US/Pacific');
var result_eastern = buggyCode();
assert.equal(result_local, result_pacific); // Might fail
assert.equal(result_pacific, result_eastern); // Definitely fails

API

• timezone_mock.register(timezone) - Replace the global Date object with a mocked one for the specified timezone. Defaults to 'US/Pacific' if no timezone is specified.
• timezone_mock.unregister() - Return to normal Date object behavior
• timezone_mock._Date - access to the original Date object for testing

Supported Timezones

Currently supported timezones are:

• US/Pacific
• US/Eastern
• UTC I found that testing on these three were enough to ensure code worked in all timezones (import factor is to test on a timezone with Daylight Saving Time if your local timezone does not).

Status

Most Date member functions are supported except for some conversions to locale-specific date strings.

With non-DST timezones, it should behave identically to the native Javascript Date object. With DST timezones, it may sometimes behave slightly differently when given an ambiguous date string (e.g. "2014-11-02 01:00:00" in "US/Pacific", is treated as 1AM PDT instead of 1AM PST - same clock time, utc timestamp off by an hour).