toolkit/devtools/gcli/source/docs/writing-tests.md@97036ab72558
toolkit/devtools/gcli/source/docs/writing-tests.md
Tue, 06 Jan 2015 21:39:09 +0100
- author
- Michael Schloh von Bennewitz <michael@schloh.com>
- date
- Tue, 06 Jan 2015 21:39:09 +0100
- branch
- TOR_BUG_9701
- changeset 8
- 97036ab72558
- permissions
- -rw-r--r--
Conditionally force memory storage according to privacy.thirdparty.isolate;
This solves Tor bug #9701, complying with disk avoidance documented in
https://www.torproject.org/projects/torbrowser/design/#disk-avoidance.
2 # Writing Tests
4 There are several sources of GCLI tests and several environments in which they
5 are run.
7 The majority of GCLI tests are stored in
8 [this repository](https://github.com/joewalker/gcli/) in files named like
9 ```./lib/gclitest/test*.js```. These tests run in Firefox, Chrome, Opera,
10 PhantomJS, and NodeJS/JsDom
12 See [Running Tests](running-tests.md) for further details.
14 GCLI comes with a generic unit test harness (in ```./lib/test/```) and a
15 set of helpers for creating GCLI tests (in ```./lib/gclitest/helpers.js```).
17 # GCLI tests in Firefox
19 The build process converts the GCLI tests to run under Mochitest inside the
20 Firefox unit tests. It also adds some
