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

169 Commits

Author SHA1 Message Date
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
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
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
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
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
Yusuke Suzuki
c124f6c037 Intl.NumberFormat v3's default roundingMode should be "halfExpand" 
The test was using "halfExpand (default)".
 2021-11-30 14:35:41 -05:00
Mike Pennisi
26f1f4567e Add tests for "Intl NumberFormat v3" proposal 
This patch is intended to cover only one aspect of the proposal for
ECMA402: the "negative sign display" feature.
 2021-11-09 13:28:42 -05:00
Mike Pennisi
396fc064d8 fixup! Add tests for "Intl NumberFormat v3" proposal 2021-11-01 12:50:38 -04:00
Mike Pennisi
c0ea82adf1 fixup! Add tests for "Intl NumberFormat v3" proposal 2021-11-01 12:50:38 -04:00
Mike Pennisi
057c8acec7 Add tests for "Intl NumberFormat v3" proposal 
This patch is intended to cover only one aspect of the proposal for
ECMA402: the "rounding mode" feature.
 2021-11-01 12:50:38 -04:00
Mike Pennisi
f527a107f2 Relax tests for resolvedOptions property ordering 
A number of tests for ECMA402 asserted the exact contents of the array
returned by various `resolvedOptions` methods. This conflicted with the
expectation that more options will be introduced by future editions of
the specification.

Update these tests to assert property order more generically in order to
accommodate implementation of future language proposals and more closely
align with similar tests.

Update all `resolvedOptions` tests to produce more meaningful error
messages (including replacing the generic `arrayContains` assertion with
a specific assertion regarding the value of the first array element).
 2021-10-29 15:19:27 -04:00
Mike Pennisi
1ad9bb7626 Improve errors in NumberFormat#formatToParts tests 
Specify a descriptive value for the previously-unused third parameter of
the `verifyFormatParts` function in order to disambiguate error
messages.

This patch was generated with the following command:

    sed -i 's/\(verifyFormatParts([^,]\+, \)\([^,]\+\))/\1\2, "\2")/g' \
      test/intl402/NumberFormat/prototype/formatToParts/signDisplay-currency-*
 2021-10-18 09:45:11 -04:00
Mike Pennisi
7ce15a19f3 Correct test descriptions 2021-10-18 09:44:53 -04:00
André Bargull
71460edfeb Add helper functions to retrieve all calendars, collations, numberingSystems, and simple sanctioned units 
And then use these helpers to replace hard-coded lists in other tests.
 2021-09-08 09:29:06 -04:00
Ujjwal Sharma
76ab0187c0 Add NumberFormat tests for OrdinaryHasInstance 
Add tests to make sure NumberFormat does not call the instanceof
operator and calls OrdinaryHasInstance instead.

Refs: https://github.com/tc39/ecma402/pull/500
 2021-02-16 12:20:50 -05:00
ExE Boss
8f904d8cc8 Set function length and name in CreateBuiltinFunction 2021-01-29 09:45:20 -05:00
Rick Waldron
82f38efbab Features: add "intl-normative-optional" 2020-11-03 14:28:17 -05:00
Yusuke Suzuki
20b11bee0f Add tests for [[Description]] of Intl [[FallbackSymbol]] 
If normative optional is implemented and [[FallbackSymbol]] is used, its description should be "IntlLegacyConstructedSymbol"
 2020-11-02 12:34:09 -05:00
Yusuke Suzuki
3c789640ec dft-currency-mnfd-range-check-mxfd.js should check maximumFractionDigits, not maximumSignificantDigits 
This test is checking maximumSignificantDigits, but this is wrong. We should check maximumFractionDigits.
 2020-09-28 09:09:09 -04:00
Yusuke Suzuki
3fe45c44c6 Revert "Intl.NumberFormat + currency will throw an error if maximumFractionDigits is less than currencyDigits" 
This reverts commit a7b9067fe129b8ded01a4b86f8295ed40fe2d9e5.
I fixed the test with a7b9067fe129b8ded01a4b86f8295ed40fe2d9e5 based on the current spec, but this test was based on WIP spec change.
 2020-09-24 14:55:28 -04:00
Yusuke Suzuki
a7b9067fe1 Intl.NumberFormat + currency will throw an error if maximumFractionDigits is less than currencyDigits 
In 12.1.1 SetNumberFormatDigitOptions step 12.d[1], mnfd (minimum fraction digits) becomes the same to currencyDigits (mxfdDefault in this case).
It is 2 for USD, 4 for CLF. So, if maximumFractionDigits is less than that, we should throw RangeError.

[1]: https://tc39.es/ecma402/#sec-setnfdigitoptions
 2020-09-15 10:33:23 -04:00
Rick Waldron
873a7241c3 Fixup Intl.* this-value tests (delete dups, add proper esid) 2020-09-14 13:35:13 -04:00
Frank Tang
ab3a86d9b3 Move tests from 
https://source.chromium.org/chromium/chromium/src/+/master:v8/test/test262/local-tests/
 2020-09-14 13:35:13 -04:00
Ujjwal Sharma
6c3f8cdc75
Update tests for tc39/ecma402#471 (#2707) 2020-08-13 10:31:24 -07:00
André Bargull
649d0d2c9a Update list of non-algorithmic numbering systems 
Per https://github.com/tc39/ecma402/pull/438
 2020-06-24 12:11:36 -04:00
André Bargull
630f7dee66 Updated expected error in NumberFormat constructor per current spec 2020-06-24 12:11:36 -04:00
Alexey Shvayka
ef12a8b11c
Intl: Add coverage for meaningful @@toStringTag values (#2634) 
* Add Intl.Collator tests

* Add Intl.DateTimeFormat tests

* Adjust Intl.NumberFormat tests

* Add Intl.PluralRules tests

* Remove now duplicated tests

* Add "toString-changed-tag.js" tests
 2020-06-01 15:40:35 -07:00
Frank Yung-Fong Tang
064d3c24e3 correct exceptions for exceptZero 2020-04-23 10:46:27 -04:00