trisquel-icecat/icecat/remote/marionette/test/xpcshell
2025-07-17 09:32:21 -06:00
..
.eslintrc.js icecat: initial release for Trisquel 12.0, Ecne 2025-07-17 09:32:21 -06:00
README icecat: initial release for Trisquel 12.0, Ecne 2025-07-17 09:32:21 -06:00
test_actors.js icecat: initial release for Trisquel 12.0, Ecne 2025-07-17 09:32:21 -06:00
test_browser.js icecat: initial release for Trisquel 12.0, Ecne 2025-07-17 09:32:21 -06:00
test_cookie.js icecat: initial release for Trisquel 12.0, Ecne 2025-07-17 09:32:21 -06:00
test_json.js icecat: initial release for Trisquel 12.0, Ecne 2025-07-17 09:32:21 -06:00
test_message.js icecat: initial release for Trisquel 12.0, Ecne 2025-07-17 09:32:21 -06:00
test_navigate.js icecat: initial release for Trisquel 12.0, Ecne 2025-07-17 09:32:21 -06:00
test_prefs.js icecat: initial release for Trisquel 12.0, Ecne 2025-07-17 09:32:21 -06:00
test_sync.js icecat: initial release for Trisquel 12.0, Ecne 2025-07-17 09:32:21 -06:00
test_web-reference.js icecat: initial release for Trisquel 12.0, Ecne 2025-07-17 09:32:21 -06:00
xpcshell.toml icecat: initial release for Trisquel 12.0, Ecne 2025-07-17 09:32:21 -06:00

To run the tests in this directory, from the top source directory,
either invoke the test despatcher in mach:

	% ./mach test remote/marionette/test/xpcshell

Or call out the harness specifically:

	% ./mach xpcshell-test remote/marionette/test/xpcshell

The latter gives you the --sequential option which can be useful
when debugging to prevent tests from running in parallel.

When adding new tests you must make sure they are listed in
xpcshell.ini, otherwise they will not run on try.

See also ../../doc/Testing.md for more advice on our other types of tests.