- Provides a mechanism to collect client-side code coverage data and combine that with browser coverage.
- Provides the ability to launch and wait for server-side components to start up before each test run.
- Provides the ability to safely shut down server-side test fixtures after each test run.
- Provides cleanup mechanisms to remove temporary browser content after each test run.
To use this grade from Testem, install this package as a development dependency using a command like
npm install --save-dev gpii-testem. Note: There is currently
a bug in newer versions of Testem, if you use anything higher than
version 1.13.0, you may experience hangs when attempting to quit Testem from the console.
use of the dynamic configuration options available via the
The most basic example of a file might look something like:
var fluid = ;fluid;var my = fluid;fluid;moduleexports = mytestem;
To make use of the code coverage support provided by gpii.testem, you must load the "coverage sender" in your HTML fixtures. See the coverage docs for details.
Browser Coverage Only
If you only want to check the coverage of browser code, you can run your tests using a command like the following:
node node_modules/testem/testem.js ci --file path/to/your-testem-config.js
If you save your configuration to the file name
testem.js in your package root, you can launch Testem using a command
node node_modules/testem/testem.js or
node node_modules/testem/testem.js ci.
Browser and Node Coverage
If you are testing browser code in combination with node code, please see the example in the Testem component docs.
For more information, check out the documentation links below:
Running the Tests in this Package
You can run the tests using the command
npm test. You are not required to have Testem installed globally to run the
A Warning about Internet Explorer 11
There is currently a bug in Testem that results in IE11 windows opened by Testem not being closed when the tests finish. Until that bug is resolved, if you are running tests from Windows, you will need to close any open IE11 windows before launching the tests.
Running (Chrome) in "Headless" Mode
If your system has a new enough version of Chrome,
you can optionally run the tests in "headless" mode by setting the
HEADLESS environment variable to a non-empty value.