gecko-dev/testing/marionette/test/unit
Andreas Tolfsen 4e7776764d Bug 1456050 - Add marionette.contentListener to MarionettePrefs. r=whimboo
MozReview-Commit-ID: 1SPrw4Vwd3N

--HG--
extra : rebase_source : f2218a9ec0ebc3472a964abcca0bd1aa09ed2eb0
2018-04-23 07:26:09 +01:00
..
.eslintrc.js Bug 1453381 - Enable eslint for Marionette xpcshell tests. r=whimboo 2018-04-11 20:27:49 +01:00
README.md Bug 1453381 - Add docs for running Marionette xpcshell tests. r=whimboo 2018-04-11 20:53:50 +01:00
test_action.js
test_assert.js
test_browser.js
test_cookie.js
test_dom.js
test_element.js
test_error.js
test_evaluate.js
test_format.js
test_message.js
test_navigate.js
test_prefs.js Bug 1456050 - Add marionette.contentListener to MarionettePrefs. r=whimboo 2018-04-23 07:26:09 +01:00
test_session.js
test_sync.js
xpcshell.ini Bug 1432894 - Provide shorthands for Marionette prefs. r=whimboo 2018-04-14 17:25:26 +01:00

README.md

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

% ./mach test testing/marionette/test/unit

Or call out the harness specifically:

% ./mach xpcshell-test testing/marionette/test/unit

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.