Magic-Mirror/gecko-dev
1
0
Fork 0
mirror of https://github.com/mozilla/gecko-dev.git synced 2024-10-08 10:44:56 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

bug 1523104: remote: update testing documentation; r=ochameau

Browse Source
This commit is contained in:
Andreas Tolfsen 2019-02-17 15:18:47 +00:00
parent 6d5672ceb8
commit 0da7f1e100
2 changed files with 32 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
remote/doc/Testing.md
View File

@ -1,19 +1,35 @@
Testing
=======
xpcshell unit tests
-------------------
The remote agent has unit- and functional tests located under
`remote/test/{unit,browser}`.
The remote agent has a set of [xpcshell] unit tests located in
_remote/test/unit_. These can be run this way:
You may run all the tests locally using `mach test` like this:
% ./mach test remote/test/unit
% ./mach test remote/test
Because tests are run in parallel and xpcshell itself is quite
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 test --sequential remote/test/unit/test_Assert.js
% ./mach xcpshell --sequential remote/test/unit/test_Assert.js
The unit tests will appear as part of the `X` jobs on Treeherder.
[xpcshell]: https://developer.mozilla.org/en-US/docs/Mozilla/QA/Writing_xpcshell-based_unit_tests
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
[browser chrome]: https://developer.mozilla.org/en-US/docs/Mozilla/Browser_chrome_tests

18
remote/test/browser/README.md
View File

@ -1,11 +1,11 @@
# Update chrome-remote-interface.js
Update chrome-remote-interface.js
=================================
Upstream instructions on (github)[https://github.com/cyrus-and/chrome-remote-interface#using-vanilla-javascript].
Upstream instructions on
https://github.com/cyrus-and/chrome-remote-interface#using-vanilla-javascript:
```
$ git clone https://github.com/cyrus-and/chrome-remote-interface.git
$ cd chrome-remote-interface
$ npm install
$ TARGET=var DEBUG=true npm run webpack
$ cp chrome-remote-interface.js ../
```
% git clone https://github.com/cyrus-and/chrome-remote-interface.git
% cd chrome-remote-interface
% npm install
% TARGET=var DEBUG=true npm run webpack
% cp chrome-remote-interface.js ../