A collection of testing helpers.
To actually run the tests, a browser must be started (if not running) and captured by the JsTestDriver server. Since we generally want to do this only once, the JsTestDriver server is started and stopped as a subprocess using zope.testing support for layers.
JsTestDriver supports outputing test results in an XML-based format, which we parse and feed into a TestResult instance from unittest.
Please refer to the JsTestDriver TestCase documentation on how to write tests that are supported by JsTestDriver.
Additionally, the lazr-js project has some examples of running YUI Test-based tests under JsTestDriver.
from lazr.testing.jstestdriver import JsTestDriverTestCase class JsTestDriverSelfTest(JsTestDriverTestCase): config_filename = os.path.abspath(os.path.join(os.path.dirname(__file__), "js", "tests.conf"))
In order to actually run the tests you need to specify the location where JsTestDriver can be found. This can be done by exporting an environment variable:
JSTESTDRIVER="java -jar /path/to/JsTestDriver.jar" ./bin/test
You can control the port used by the server with another environment variable. The default is to start the server on port 4224:
It is also possible (and very handy!) to have a long-running JsTestDriver server and connect one or more browser to it manually. If you want to do that, you have to export another variable telling where your JsTestDriver server is running (hint: this could even be a remote server):
Controlling the browser that will be started can also be done by setting the BROWSER environment variable to the full path of your browser’s executable.
If your default browser is Firefox, it can be annoying that every time you run the tests in the background a new tab opens and Firefox switches to it automatically, disrupting your browsing. You can disable that by Preferences -> Tabs and disabling the option named “When I open a link in a new tab, switch to it immediately”. It might be also interesting to enable the option “Open new windows in a new tab instead” if it’s not enabled yet.
Finally, if you’re just too annoyed that every test run opens new tabs, you have the option of having a long-running JsTestDriver server as described above and manually connect to it. That way, only a single tab of your browser will be used and every test run will re-use that tab.
- Add compatibility with JsTestDriver 1.2.2. Not compatible with earlier versions of JsTestDriver anymore.
- Don’t wait for a browser, if JsTestDriverLayer doesn’t start the browser. (LP: #627413)
- Brown bag, botched NEWS release.
- Initial release