A test runner that allows you to tag your tests and execute specific groups of tests with Jest. This runner is based on the original repository that was archived
npm i -D jest-runner-groups
To use this runner you need to tag your tests, add this runner to your jest config and update your test command to specify which groups to run.
To properly tag your tests, you need to add a docblock with the @group
tag to every test file you have. For example, your test should look like the following to belong to the unit/classes/foo
group:
/**
* Tests Foo class
*
* @group unit/classes/foo
*/
import Foo from '../src/Foo';
describe( 'Foo class', () => {
it( '...', () => {
...
} );
...
} );
Your tests may have multiple groups per file:
/**
* Admin dashboard tests
*
* @group admin/pages/dashboard
* @group puppeteer
* @group acceptance
*/
describe( 'Dashboard page', () => {
...
} );
To make Jest use this runner, you need to update your Jest config and add groups
runner to it. For example, if your jest config is in the package.json
file:
{
"name": "my-package",
"version": "1.0.0",
"dependencies": {
},
"jest": {
"runner": "jest-runner-grouped-tests"
}
}
Or in the jest.config.js
file:
module.exports = {
...
runner: "jest-runner-grouped-tests"
};
Note: There is a confusion between runner and testRunner options in the jest configuration. The main difference between them is that jest uses
runner
to find and execute all tests, andtestRunner
to execute a particular test file. So, if you want to usejest-circus
, then add it astestRunner
along with"runner": "groups"
option and they will work together.
Once you update your tests and jest config, you can start running tests in groups by using --group
argument. Just specify a group or groups that you want to run like this:
// using jest executable:
jest --group=unit
// or via npm:
npm test -- --group=unit
You can use multiple --group
arguments to specify multiple groups to run:
npm test -- --group=unit/classes --group=unit/services
Also pay attention that if you specify a prefix of a group, then all tests that have a group that starts with that prefix will be executed. In other words, if you run npm test -- --group=unit
command, then all tests that have a group that starts with unit
will be executed.
If you want to exclude a subgroup from being executed, add minus character to the beginnig of its name. The following example shows how to run all tests in the foo
group, but exclude foo/baz
group:
jest --group=foo --group=-foo/baz
When you run your tests using jest-runner-groups, you can check which group is currently running by checking the current process environment variables. This can be handy if you want to use different fixtures for different groups or skip a certain functionality for a specific group.
Each group is added with the JEST_GROUP_
prefix and all non-word characters in the group name are replaced with underscores. For example, if you run the following command:
npm test -- --group=unit/classes --group=unit/services
Then you can check groups in your jest tests:
/**
* Admin dashboard tests
*
* @group unit/classes
* @group unit/services
* @group unit/utility
*/
it( '...', () => {
expect( process.env.JEST_GROUP_UNIT_CLASSES ).toBeTruthy();
expect( process.env.JEST_GROUP_UNIT_SERVICES ).toBeTruthy();
expect( process.env.JEST_GROUP_UNIT_UTILITY ).not.toBeTruthy();
} );
You can use --regex
argument to specify multiple groups by a regular expression:
jest --regex=foo/.\*
You can use multiple --regex
arguments:
jest --regex=foo/.\* --regex=bar\|baz
Or use both --regex
and --group
:
jest --regex=foo/.\* --group=bar
If you want to exclude tests from being executed, add minus character to the beginnig of your regular expression.
The following example shows how to run all tests with a group's name contains foo
, but exclude all groups that foo/baz/.*
match their name:
jest --regex=foo --regex=-foo/baz/.\*
The mustIncludeGroups functionality allows you to specify groups that must be included for a test to be run. If any of these groups are missing from the test's tags, the test will be excluded from the run. This is useful for ensuring certain essential groups are always included in the test execution criteria.
To use the mustIncludeGroups functionality, add the ! prefix to the group name in the command line argument. For example, if you want to run tests that must include the core group:
jest --group=unit --group=!core
You can combine mustIncludeGroups with other group and regex arguments for more refined control:
jest --group=unit --group=!core --regex=foo/.*
Want to help or have a suggestion? Open a new ticket and we can discuss it or submit a pull request.
MIT