tenfourfox/js/src/jit-test
Cameron Kaiser 55284dd803 update ESR base to 115; update EV roots, certs, HSTS, pins, TLDs, TZs; update usrsctp; security pullup; more comprehensive nuisance script blocking; fixes for #488, #566 2023-08-31 00:30:32 -07:00
..
etc hello FPR 2017-04-19 00:56:45 -07:00
lib #430: implement destructuring default arguments from M932080 +test changes 2017-08-23 20:48:44 -07:00
manual-tests hello FPR 2017-04-19 00:56:45 -07:00
modules hello FPR 2017-04-19 00:56:45 -07:00
tests update ESR base to 115; update EV roots, certs, HSTS, pins, TLDs, TZs; update usrsctp; security pullup; more comprehensive nuisance script blocking; fixes for #488, #566 2023-08-31 00:30:32 -07:00
README hello FPR 2017-04-19 00:56:45 -07:00
jit_test.py #393: bustage fix 2017-05-12 10:42:55 -07:00

README

JS Trace Test Suite

* PURPOSE

This is a test suite for testing TraceMonkey. All tests are run in the JS shell
with tracing enabled (-j).

* REQUIREMENTS

Python 2.5. This is already a standard requirement for building our tree.

* RUNNING THE TESTS

Basic usage:

    python jit_test.py <path-to-js-shell>

The progress bar shows [#tests passed, #tests failed, #tests run] at the left.
If all tests pass, the output is 'PASSED ALL'. The test suite can be interrupted
at any time with Ctrl+C and partial results will be printed.

To run only the basic tests, not including the slow tests:

    python jit_test.py <path-to-js-shell> basic

For more options:

    python jit_test.py -h

* CREATING NEW TESTS

Simply create a JS file under the 'tests/' directory. Most tests should go in
'tests/basic/'.

All tests are run with 'lib/prologue.js' included first on the command line. The
command line also creates a global variable 'libdir' that is set to the path
of the 'lib' directory. To include a file 'foo.js' from the lib directory in a 
test case:

    load(libdir + 'foo.js')

* TEST METALINES

The first line of a test case can contain a special comment controlling how the
test is run. For example:

    // |jit-test| allow-oom;

The general format in EBNF is:

    metaline  ::= cookie { item ";" }
    cookie    ::= "|jit-test|"
    item      ::= flag | attribute

    flag      ::= "slow" | "allow-oom" | "valgrind" | "tz-pacific" |
                  "ion-eager" | "debug" |
                  "dump-bytecode" |


    attribute ::= name ":" value
    name      ::= "error" | "exitstatus"
    value     ::= <string>

The metaline may appear anywhere in the first line of the file: this allows it
to be placed inside any kind of comment.

The meaning of the items:

    slow         Test runs slowly. Do not run if the --no-slow option is given.
    allow-oom    If the test runs out of memory, it counts as passing.
    valgrind     Run test under valgrind.
    tz-pacific   Always run test with the Pacific time zone (TZ=PST8PDT).
    ion-eager    Run js with --ion-eager, whether --jitflags says to or not
    debug        Run js with -d, whether --jitflags says to or not
    dump-bytecode Run js with -D, whether --jitflags says to or not

    error        The test should be considered to pass iff it throws the
                 given JS exception.
    exitstatus   The test should exit with the given status value (an integer).

* END