blob: 2e6774c85eda38d9a0b1e7a6f29492ffef1aa849 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
|
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
by Tinderbox. 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
https://developer.mozilla.org/en-US/docs/SpiderMonkey/Creating_JavaScript_tests
Adding a test
-------------
Drop it in an appropriate directory under the tests directory.
<fineprint> Some names are forbidden. Do not name your test browser.js,
shell.js, template.js, user.js, js-test-driver-begin.js, or
js-test-driver-end.js, or any of the names of the files in supporting/.
</fineprint>
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:
http://dxr.mozilla.org/mozilla-central/source/layout/tools/reftest/README.txt
Example:
// |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>
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.
Running tests
-------------
See
https://developer.mozilla.org/en-US/docs/SpiderMonkey/Running_Automated_JavaScript_Tests
|
