db3d0486e7
Summary: Not being able to have timestamps in Jest snapshots, as they would differ across machines required jumping through a lot of hoops. Run this into once again more by a test suite that didn't trigger on CI, but failed for me locally. With this fix everyone can happily commit time based snapshots and they will always be assumed to be running in UTC :) Reviewed By: nikoant Differential Revision: D29025759 fbshipit-source-id: 426d1b065afdd4a2ed75b47203b13fff0ece1272
33 lines
1.1 KiB
JavaScript
33 lines
1.1 KiB
JavaScript
/**
|
|
* Copyright (c) Facebook, Inc. and its affiliates.
|
|
*
|
|
* This source code is licensed under the MIT license found in the
|
|
* LICENSE file in the root directory of this source tree.
|
|
*
|
|
* @format
|
|
*/
|
|
|
|
// import/no-unresolved complains, although it is a perfectly fine import
|
|
// eslint-disable-next-line
|
|
global.fetch = require('jest-fetch-mock');
|
|
|
|
// make sure test run everywhere in the same timezone!
|
|
// +11, somewhere in the middle of nowhere, so this deviates for everyone and will fail early :)
|
|
const timezone = 'Pacific/Pohnpei';
|
|
if (process.env.TZ !== timezone) {
|
|
throw new Error(
|
|
`Test started in the wrong timezone, got ${process.env.TZ}, but expected ${timezone}. Please use the package.json commands to start Jest, or prefix the command with TZ=${timezone}`,
|
|
);
|
|
}
|
|
|
|
// Make sure we have identical formatting of Dates everywhere
|
|
const toLocaleString = Date.prototype.toLocaleString;
|
|
// eslint-disable-next-line no-extend-native
|
|
Date.prototype.toLocaleString = function (_locale, ...args) {
|
|
return toLocaleString.call(this, 'en-US', ...args);
|
|
};
|
|
|
|
require('immer').enableMapSet();
|
|
|
|
require('../app/src/fb-stubs/Logger').init(undefined, {isTest: true});
|