author André Bargull <andre.bargull@gmail.com>
Thu, 07 Mar 2019 14:42:25 +0000
changeset 520766 c450f92d5e6219e962e8c5219a0d7c5348b813cb
parent 449065 7a962f0ad70811d0fcafe49b2ffe602f6c76eb18
permissions -rw-r--r--
Bug 1531202 - Part 1: Don't prepend reftest entries in test262 'raw' tests. r=jwalden - Add separate function to import fixture files instead of treating them like test files. This simplifies the code structure a bit and avoids unnecessary output spew, because the test262 test record parser no longer complains about missing yaml frontmatter. - Write reftest terms into a new test262/jstests.list file for raw tests. - Allow including nested jstests.list files in _parse_external_manifest. Differential Revision: https://phabricator.services.mozilla.com/D21677

JS Test Suite Readme

The JS test suite is a fairly extensive collection of correctness and regression
tests for the Spidermonkey engine. Two harnesses run these tests: the shell test
harness in this directory and the "reftest" harness built into the browser, used
in continuous integration. The browser reftests require additional manifest files; these are
generated automatically by the build phase 'package-tests' using the
'--make-manifests' option to jstests.py.

Creating a test
For general information, see

Adding a test
    Drop your test file in an appropriate directory under js/src/tests/non262/.

        <fineprint> Some names are forbidden. Do not name your test browser.js,
        shell.js, template.js, user.js, js-test-driver-begin.js, or

Test262, ECMAScript conformance tests

    The js/src/tests/test262/ folder contains tests imported from the ECMAScript
    conformance test suite: https://github.com/tc39/test262. To update the test
    suite to get the latest version (including tests of new ECMAScript features
    or feature proposals), you can use the updater script:


    Additionally, you can find the test262-export.py script to export tests to
    the test262 format for potential contribution to test262.

Adjusting when and how a test runs
    Put a comment at the top of the header matching the format:
        // |reftest| <failure-type> -- <comment>

    Where <failure-type> is a standard reftest <failure-type> string, as documented by:

        // |reftest| skip-if(!xulRuntime.shell) -- does not always dismiss alert

        <fineprint> Either // or /* */ style comments may be used. The entire
        comment must appear in the first 512 bytes of the file. The control
        string must be in its own comment block. </fineprint>

    When adding such comments to individual files is not feasible (e.g., for
    imported tests), reftest manifest entries can be added to jstests.list
    instead. Combining in-file comments with entries in this manifest file for
    the same files is not supported (the one from the manifest file will be
    used). Only the following two forms are supported:
        <failure-type> include <relative_path>
        <failure-type> script <relative_path>
        include <relative_path>
    The <type> "include" indicates that <failure-type> should apply to all test
    cases within a directory. A statement for a nested directory or script
    overrides one for an enclosing directory. The <type> "include" without a
    <failure-type> recursively loads another jstests.list file for further

Running tests