tyler.durden/test262
1
0
Fork 0
mirror of https://github.com/tc39/test262.git synced 2025-07-31 01:44:54 +02:00
Code Issues Packages Projects Releases Wiki Activity
5,646 Commits 18 Branches 0 Tags
Commit Graph

517 Commits

Author SHA1 Message Date
Jesse Alama
7d82f8ac63 Add tests for invalid extended year "-000000" 
https://github.com/tc39/proposal-temporal/issues/1753 records the
consensus reached at the October 2021 TC39 meeting to disallow "-000000"
as an extended year, both in Date.parse and Temporal. This adds tests for
the Temporal part of that.
 2022-02-01 17:59:02 -05:00
Ms2ger
158d0bf35f Test PlainYearMonth constructor, from. 2022-01-28 13:17:31 -05:00
Romulo Cintra
ffae81a3f6 update assert name and length check 2022-01-26 16:32:15 -05:00
Romulo Cintra
034e5dd201 Update test/intl402/DurationFormat/instance/length.js 
Thanks

Co-authored-by: Ms2ger <Ms2ger@gmail.com>
 2022-01-26 16:32:15 -05:00
Romulo Cintra
95613d4ec8 update DurationFormat tests 2022-01-26 16:32:15 -05:00
Ms2ger
d86b913c11 Test Temporal.Now. 2022-01-24 13:36:43 -05:00
Romulo Cintra
66f4071495 update test 2022-01-24 13:28:44 -05:00
Romulo Cintra
e687842030 update tests 2022-01-24 13:28:44 -05:00
Romulo Cintra
9f8ac1aace add instance checks 2022-01-24 13:28:44 -05:00
Philip Chimento
631337b261 Remove duplication between built-ins/ and intl402/ 
There were two cases where tests in intl402/ had some duplication of tests
that are in built-ins/ as well. Remove this duplication, and restrict the
intl402/ tests to testing things that can't be tested on all hosts.
 2022-01-19 13:47:43 -05:00
Philip Chimento
a6faa8c000 Add tests using Intl time zones to intl402/ 
For cases in the previous commit that actually removed some functionality
from tests in built-ins/, add corresponding tests in intl402/ to preserve
test coverage of that functionality for hosts that do support Intl.
 2022-01-19 13:47:43 -05:00
Yusuke Suzuki
1935e1b410 Fix Intl.NumberFormat useGrouping value tests 
After Intl.NumberFormat v3, default useGrouping is "auto".
We also fix test/intl402/NumberFormat/test-option-useGrouping.js. After v3,
it accepts string and boolean.
 2022-01-19 13:46:58 -05:00
Frank Yung-Fong Tang
9aedfd146d replace SPACE with NBSP 
the " " before the currency symbol and between group are actually nbsp not SPACE.
 2022-01-07 13:21:05 -05:00
Frank Yung-Fong Tang
16f3f494d3 fix test 
1. "–" => " – "
2. Move the verifyProperty after assert.sameValue because it has side effect of removing that property while it is writable.
 2022-01-07 13:20:17 -05:00
Frank Yung-Fong Tang
b91167622b add includes: [propertyHelper.js] 2022-01-07 13:20:17 -05:00
Frank Yung-Fong Tang
0b8efb9c0d correct expectation 2022-01-07 13:19:07 -05:00
Frank Yung-Fong Tang
a12f375a99 remove extra "Digits" 2022-01-07 13:19:07 -05:00
Frank Yung-Fong Tang
fe9f29e4a8 Fix format-rounding-priority-less-precision.js 
1. remove extra "Digits" in the spelling
2. fix the setting of minimumSignificantDigits is more precise since both will produce "1.00" w/o change
 2022-01-07 13:19:07 -05:00
Frank Yung-Fong Tang
a665b5f3a2 fix case for roudingIncrement: 5000 2022-01-07 13:19:07 -05:00
Frank Yung-Fong Tang
4cc44841f6 fix test for roundingIncrement: 500 2022-01-07 13:19:07 -05:00
Frank Yung-Fong Tang
5ee4e0d609 change to minimumFractionDigits:1 2022-01-07 13:19:07 -05:00
Frank Yung-Fong Tang
a8e89964b4 set minimumFractionDigits: 1 to testing of 250 2022-01-07 13:19:07 -05:00
Frank Yung-Fong Tang
2d52f74d97 set minimumFractionDigits: 1 2022-01-07 13:19:07 -05:00
Frank Yung-Fong Tang
4719c8c2dd adjuest setting for roundingIncrement: 25 2022-01-07 13:19:07 -05:00
Frank Yung-Fong Tang
9e50891a40 set minimumFractionDigits: 1 in format-rounding-increment-5 
We need to set minimumFractionDigits: 1 for the case of {roundingIncrement: 5, maximumFractionDigits: 1} and also adjust the test expectation. 
Otherwise, inside testNumberFormat , it will call   getPatternParts to format 1.1 and -1.1 and cause pattern mismatch (because the result will be "1" instead of "1.1" in that configuration)

https://github.com/tc39/test262/blob/main/harness/testIntl.js#L2369
 2022-01-07 13:19:07 -05:00
Frank Yung-Fong Tang
63f2c5b10f Remove 1.1 case which should NOT throw RangeError 
roundingIncrement: 1.1 will not throw RangeError because
1.  roundingIncrement is read by calling GetNumberOption 
2. GetNumberOption https://tc39.es/ecma402/#sec-getnumberoption will call DefaultNumberOption https://tc39.es/ecma402/#sec-defaultnumberoption and 
3. DefaultNumberOption will call floor() in step 3.
 2022-01-07 13:18:18 -05:00
Frank Yung-Fong Tang
0fe508c5f0 change notation to "standard" 
I do not believe this setup is correct if we use notation: "compact". 

in https://tc39.es/proposal-intl-numberformat-v3/out/numberformat/diff.html#sec-setnfdigitoptions
notation is "compact"
mnsd is undefined
mxsd is undefined
mnfd is undefined
mxfd is undefined
hasSd is false
hasFd is false
needSd is false
needFd is false
so step 23 else block will be run
Set intlObj.[[RoundingType]] to morePrecision.
then in step 23 of https://tc39.es/proposal-intl-numberformat-v3/out/numberformat/diff.html#sec-initializenumberformat
```
If roundingIncrement is not 1 and numberFormat.[[RoundingType]] is not fractionDigits, throw a RangeError exception.
```
 2022-01-07 13:17:50 -05:00
Mike Pennisi
6c9b4de507 fixup! Add tests for "Intl NumberFormat v3" proposal 2022-01-04 09:35:13 -05:00
Mike Pennisi
d071b37f09 Add tests for "Intl NumberFormat v3" proposal 
This patch is intended to cover only one aspect of the proposal for
ECMA402: the "new rounding/precision options" feature.
 2022-01-04 09:35:13 -05:00
Yusuke Suzuki
6804e59f9f Fix Intl.PluralRules.selectRange test 
en-US's Intl.PluralRules.selectRange(102, 201) is "other", not "few".
 2022-01-04 09:33:18 -05:00
Romulo Cintra
46f847c2e8
NumberFormat v3 tests (#3283) 
* feat: nfv3 plural rules

* test NaN and out of range values

* add NumberFormat v3 proposal features

* add feature to selectrange tests

* add basic test NumberFormat.formatRange

* add basic test NumberFormat.formatRangeToParts

* update Plural Rules tests

* refactor some tests

* update formatRange tests

* update formatRangeToParts tests

* update feature flag

* add locale: [en-US]

* update selectRange tests

* update tests

* update en-US tests and add pt-PT

* update prop-desc check

* validate  1.1.25_4.a

Co-authored-by: Romulo Cintra <romulocintra@gmqil.com>
 2021-12-17 14:33:27 -05:00
Philip Chimento
0184842b09 Test rejection of "Z" UTC designators in Plain strings 
Tests for the normative changes made to Temporal in
https://github.com/tc39/proposal-temporal/pull/1874
 2021-12-14 13:39:19 -05:00
Frank Yung-Fong Tang
29a0a1e253 Simplify the testing 
The last five lines below are simply WRONG and not according to the spec. 

```
const durationFormat = new Intl.DurationFormat();

verifyNotEnumerable(durationFormat, Symbol.toStringTag);
verifyNotWritable(durationFormat, Symbol.toStringTag);
verifyConfigurable(durationFormat, Symbol.toStringTag);
```
 2021-12-14 13:37:35 -05:00
Frank Yung-Fong Tang
b9cac998df Correct set up 2021-12-14 10:39:37 -05:00
Frank Yung-Fong Tang
6fecbe5257 correct test result in NumberFormat/...value-decimal-string.js 2021-12-14 10:39:37 -05:00
Frank Tang
c2bd148ac7 restore the wrong copy 2021-12-06 09:12:27 -05:00
Frank Tang
78907d6393 Move toLocaleString testing to intl402 
Move part of the test of toLocaleString which depends on
15 Amendments to the ECMAScript® 2021 Internationalization API Specification
to intl402. Keep behavior specified in earlier chapters in built-ins
 2021-12-06 09:12:27 -05:00
Nikhil Singhal
1f16a6ad0e docs: update features 2021-12-03 19:53:31 -05:00
Nikhil Singhal
f00ea58ae9 test(Intl.DurationFormat.prototype): check prototype attributes 2021-12-03 19:53:31 -05:00
jugglinmike
4d23bbf00a
Add tests for "Intl NumberFormat v3" proposal (#3307) 
* Add tests for "Intl NumberFormat v3" proposal

This patch is intended to cover only one aspect of the proposal for
ECMA402: the "interpret strings as decimals" feature.

* fixup! Add tests for "Intl NumberFormat v3" proposal
 2021-12-03 19:51:57 -05:00
Frank Yung-Fong Tang
a3a31f0316 Move test with IATA TimeZone to intl402 2021-12-02 09:46:33 -05:00
Frank Yung-Fong Tang
fdad35e658 Move IATA TimeZone test to intl402 2021-12-02 09:46:33 -05:00
Frank Yung-Fong Tang
00369cfe38 Move test under intl402 2021-12-02 09:46:33 -05:00
Frank Yung-Fong Tang
ef697bbc6d fix en-IN expectation 2021-12-02 09:45:59 -05:00
Frank Yung-Fong Tang
54ef0b1bf4 Fix expectation of "compact" notation 2021-12-02 09:45:59 -05:00
Mike Pennisi
ae9440df36 fixup! Add tests for "Intl NumberFormat v3" proposal 2021-11-30 14:52:57 -05:00
Mike Pennisi
ef78452924 Add tests for "Intl NumberFormat v3" proposal 
This patch is intended to cover only one aspect of the proposal for
ECMA402: the "grouping enum" feature. It also includes coverage for the
formatting option as already defined by the latest version of ECMA402.
 2021-11-30 14:52:57 -05:00
André Bargull
666d62a27f Correct negative-zero sign display tests 
The negative sign is computed after rounding, so when the input `-0.0001` is
rounded to `-0`, the expected result should be `"0"` instead of `"-0"`.
 2021-11-30 14:51:22 -05:00
Frank Yung-Fong Tang
a171df1c03 rollback changes get into the wrong branch 2021-11-30 14:49:23 -05:00
Frank Yung-Fong Tang
4d831016c3 Fix expectation for "Asia/Ulan_Bator" 2021-11-30 14:49:23 -05:00