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.

michael@0 1
michael@0 2 # Writing Tests
michael@0 3
michael@0 4 There are several sources of GCLI tests and several environments in which they
michael@0 5 are run.
michael@0 6
michael@0 7 The majority of GCLI tests are stored in
michael@0 8 [this repository](https://github.com/joewalker/gcli/) in files named like
michael@0 9 ```./lib/gclitest/test*.js```. These tests run in Firefox, Chrome, Opera,
michael@0 10 PhantomJS, and NodeJS/JsDom
michael@0 11
michael@0 12 See [Running Tests](running-tests.md) for further details.
michael@0 13
michael@0 14 GCLI comes with a generic unit test harness (in ```./lib/test/```) and a
michael@0 15 set of helpers for creating GCLI tests (in ```./lib/gclitest/helpers.js```).
michael@0 16
michael@0 17 # GCLI tests in Firefox
michael@0 18
michael@0 19 The build process converts the GCLI tests to run under Mochitest inside the
michael@0 20 Firefox unit tests. It also adds some

mercurial