Confirmed users
446
edits
User:Waldo/Internationalization API: Difference between revisions
Jump to navigation
Jump to search
Discuss the Intl test-skipping mechanism
m (Slight changes/elaboration of the Language Tag section info) |
(Discuss the Intl test-skipping mechanism) |
||
| Line 156: | Line 156: | ||
The Test402 conformance test suite can be updated by Ecma members with contribution agreements at any time. Updates should be announced on the [https://mail.mozilla.org/listinfo/test262-discuss test262-discuss mailing list]. To import the updates, run the {{source|js/src/tests/update-test402.sh}} script. | The Test402 conformance test suite can be updated by Ecma members with contribution agreements at any time. Updates should be announced on the [https://mail.mozilla.org/listinfo/test262-discuss test262-discuss mailing list]. To import the updates, run the {{source|js/src/tests/update-test402.sh}} script. | ||
SpiderMonkey won't always pass all official tests, so a mechanism for marking tests as failing is needed. The mechanism by which JS tests are run is to generate test lists, then process extra jstests.list files already present and merge in their changes. The resulting data determines what tests will be packaged up, to be run as J builds on tinderbox. Thus to skip internationalization tests that fail, we list and skip them in {{source|js/src/tests/jstests.list}}. One benefit of this is that we can fix such failures without having to rerun the import script and without having to change failing tests themselves. (Arguably jstests.list used this way is a kludge, to be sure. But it's not too bad as hacks go.) | |||
=== Known issues === | === Known issues === | ||