gecko-dev/remote/doc/Testing.md
Andreas Tolfsen 86da122b28 bug 1546933: remote: drop unnecessary flags for ./mach test; r=me a=doc
The tests are instrumented to automatically set the remote.enabled
preference as part of their manifests. In the case of xpcshell,
it is also technically not need it as they do not trigger the
command-line-handler.js code path.

DONTBUILD
2019-04-25 11:52:52 +01:00

919 B

Testing

The remote agent has unit- and functional tests located under remote/test/{unit,browser}.

You may run all the tests locally using mach test like this:

% ./mach test remote/test

The tests are currently not run on try.

Unit tests

Because tests are run in parallel and xpcshell itself is quite chatty, it can sometimes be useful to run the tests in sequence:

% ./mach xcpshell-test --sequential remote/test/unit/test_Assert.js

The unit tests will appear as part of the X jobs on Treeherder.

Functional tests

We also have a set of functional browser chrome tests located under remote/test/browser:

% ./mach mochitest -f browser remote/test/browser/browser_cdp.js