
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
gpii-testem
Advanced tools
gpii.testemThis library provides a Fluid component and static functions that assist in using Testem.
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.
Once you have Testem installed, you will need to create a javascript configuration file, which will allow you to make
use of the dynamic configuration options available via the testem.js
file.
The most basic example of a file might look something like:
var fluid = require("infusion");
fluid.require("%gpii-testem");
var my = fluid.registerNamespace("my");
fluid.defaults("my.testem.grade", {
gradeNames: ["gpii.testem"],
testPages: ["tests/my-awesome-test.html"]
});
module.exports = my.testem.grade().getTestemOptions();
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.
Once you have created your configuration javascript file, you can launch Testem with your configuration.
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
like node node_modules/testem/testem.js or node node_modules/testem/testem.js ci.
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:
You can run the tests using the command npm test. You are not required to have Testem installed globally to run the
tests.
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.
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.
FAQs
A library to assist in using Testem within the Fluid ecosystem.
The npm package gpii-testem receives a total of 85 weekly downloads. As such, gpii-testem popularity was classified as not popular.
We found that gpii-testem demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.