test262/test/built-ins/Temporal/ZonedDateTime/compare/argument-propertybag-calendar-leap-second.js
Philip Chimento 078f3e22a4 Regularize leap second tests
Everywhere an ISO string is accepted in Temporal, a seconds value of :60
should always be coerced to :59, because of how leap seconds are handled
in ISO strings.

In property bags, a 'seconds: 60' property is not subject to that rule: it
should be handled according to the overflow option if there is one.

These tests existed already for some types; regularize them and add the
ones that didn't exist yet.
2022-05-03 08:18:02 +02:00

25 lines
1.3 KiB
JavaScript

// Copyright (C) 2022 Igalia, S.L. All rights reserved.
// This code is governed by the BSD license found in the LICENSE file.
/*---
esid: sec-temporal.zoneddatetime.compare
description: Leap second is a valid ISO string for a calendar in a property bag
features: [Temporal]
---*/
const timeZone = new Temporal.TimeZone("UTC");
const datetime = new Temporal.ZonedDateTime(217_123_200_000_000_000n, timeZone);
const calendar = "2016-12-31T23:59:60+00:00[UTC]";
let arg = { year: 1976, monthCode: "M11", day: 18, timeZone, calendar };
const result1 = Temporal.ZonedDateTime.compare(arg, datetime);
assert.sameValue(result1, 0, "leap second is a valid ISO string for calendar (first argument)");
const result2 = Temporal.ZonedDateTime.compare(datetime, arg);
assert.sameValue(result2, 0, "leap second is a valid ISO string for calendar (second argument)");
arg = { year: 1976, monthCode: "M11", day: 18, timeZone, calendar: { calendar } };
const result3 = Temporal.ZonedDateTime.compare(arg, datetime);
assert.sameValue(result3, 0, "leap second is a valid ISO string for calendar (nested property, first argument)");
const result4 = Temporal.ZonedDateTime.compare(datetime, arg);
assert.sameValue(result4, 0, "leap second is a valid ISO string for calendar (nested property, second argument)");