@cypress/grep
Advanced tools
@cypress/grep is a plugin for Cypress that allows you to filter and run specific tests based on tags or regular expressions. This can be particularly useful for running subsets of tests in large test suites, improving test run times, and organizing tests more effectively.
Tagging Tests
This feature allows you to tag your tests with specific labels and then run only the tests that match those tags. This is useful for running specific subsets of tests, such as smoke tests or regression tests.
```js
// In your test file
it('should do something important', { tags: ['smoke', 'regression'] }, () => {
// test code here
});
// In your Cypress configuration or command line
cypress run --env grepTags=smoke
```Filtering Tests with Regular Expressions
This feature allows you to filter and run tests based on a regular expression. This can be useful for running tests that match a specific pattern in their names or descriptions.
```js
// In your test file
it('should do something important', () => {
// test code here
});
// In your Cypress configuration or command line
cypress run --env grep='important'
```Combining Tags and Regular Expressions
This feature allows you to combine both tags and regular expressions to filter and run tests. This provides a more granular control over which tests to run, making it easier to manage large test suites.
```js
// In your test file
it('should do something important', { tags: ['smoke', 'regression'] }, () => {
// test code here
});
// In your Cypress configuration or command line
cypress run --env grepTags=smoke --env grep='important'
```Mocha is a feature-rich JavaScript test framework running on Node.js and in the browser, making asynchronous testing simple and fun. Mocha allows you to use tags and regular expressions to filter tests, similar to @cypress/grep, but it is more general-purpose and not specifically designed for Cypress.
Jest is a delightful JavaScript Testing Framework with a focus on simplicity. It works with projects using Babel, TypeScript, Node.js, React, Angular, Vue.js, and Svelte. Jest also supports test filtering using tags and regular expressions, similar to @cypress/grep, but it is more general-purpose and not specifically designed for Cypress.
Karma is a test runner for JavaScript that runs on Node.js. It allows you to execute tests in multiple real browsers. Karma supports filtering tests using regular expressions, similar to @cypress/grep, but it is more general-purpose and not specifically designed for Cypress.
Filter tests using substring
# run only tests with "hello" in their names
npx cypress run --env grep=hello
✓ hello world
- works
- works 2 @tag1
- works 2 @tag1 @tag2
1 passing (38ms)
3 pending
All other tests will be marked pending, see why in the Cypress test statuses blog post.
If you have multiple spec files, all specs will be loaded, and every test will be filtered the same way, since the grep is run-time operation and cannot eliminate the spec files without loading them. If you want to run only specific tests, use the built-in --spec CLI argument.
Table of Contents
Assuming you have Cypress installed, add this module as a dev dependency.
# using NPM
npm i -D @cypress/grep
# using Yarn
yarn add -D @cypress/grep
Note: @cypress/grep only works with Cypress version >= 10.
required: load this module from the support file or at the top of the spec file if not using the support file. You import the registration function and then call it:
// cypress/support/e2e.js
// load and register the grep feature using "require" function
// https://github.com/cypress-io/cypress/tree/develop/npm/grep
const registerCypressGrep = require('@cypress/grep')
registerCypressGrep()
// if you want to use the "import" keyword
// note: `./index.d.ts` currently extends the global Cypress types and
// does not define `registerCypressGrep` so the import path is directly
// pointed to the `support.js` file
import registerCypressGrep from '@cypress/grep/src/support'
registerCypressGrep()
// "import" with `@ts-ignore`
// @see error 2306 https://github.com/microsoft/TypeScript/blob/3fcd1b51a1e6b16d007b368229af03455c7d5794/src/compiler/diagnosticMessages.json#L1635
// @ts-ignore
import registerCypressGrep from '@cypress/grep'
registerCypressGrep()
optional: load and register this module from the config file:
// cypress.config.js
{
e2e: {
setupNodeEvents(on, config) {
require('@cypress/grep/src/plugin')(config);
return config;
},
}
}
Installing the plugin via setupNodeEvents() is required to enable the grepFilterSpecs feature.
You can filter tests to run using part of their title via grep, and via explicit tags via grepTags Cypress environment variables.
Most likely you will pass these environment variables from the command line. For example, to only run tests with "login" in their title and tagged "smoke", you would run:
Here are a few examples:
# run only the tests with "auth user" in the title
$ npx cypress run --env grep="auth user"
# run tests with "hello" or "auth user" in their titles
# by separating them with ";" character
$ npx cypress run --env grep="hello; auth user"
# run tests tagged @fast
$ npx cypress run --env grepTags=@fast
# run only the tests tagged "smoke"
# that have "login" in their titles
$ npx cypress run --env grep=login,grepTags=smoke
# only run the specs that have any tests with "user" in their titles
$ npx cypress run --env grep=user,grepFilterSpecs=true
# only run the specs that have any tests tagged "@smoke"
$ npx cypress run --env grepTags=@smoke,grepFilterSpecs=true
# run only tests that do not have any tags
# and are not inside suites that have any tags
$ npx cypress run --env grepUntagged=true
You can use any way to modify the environment values grep and grepTags, except the run-time Cypress.env('grep') (because it is too late at run-time). You can set the grep value in the cypress.json file to run only tests with the substring viewport in their names
{
"env": {
"grep": "viewport"
}
}
You can also set the env.grep object in the plugin file, but remember to return the changed config object:
// cypress/plugin/index.js
module.exports = (on, config) => {
config.env.grep = 'viewport'
return config
}
You can also set the grep and grepTags from the DevTools console while running Cypress in the interactive mode cypress open, see DevTools Console section.
# run all tests with "hello" in their title
$ npx cypress run --env grep=hello
# run all tests with "hello world" in their title
$ npx cypress run --env grep="hello world"
You can pass multiple title substrings to match separating them with ; character. Each substring is trimmed.
# run all tests with "hello world" or "auth user" in their title
$ npx cypress run --env grep="hello world; auth user"
The filter is also applied to the "describe" blocks. In that case, the tests look up if any of their outer suites are enabled.
describe('block for config', () => {
it('should run', () => {})
it('should also work', () => {})
})
# run any tests in the blocks including "config"
--env grep=config
Note: global function describe and context are aliases and both supported by this plugin.
# run all tests WITHOUT "hello world" in their title
$ npx cypress run --env grep="-hello world"
# run tests with "hello", but without "world" in the titles
$ npx cypress run --env grep="hello; -world"
Note: Inverted title filter is not compatible with the grepFilterSpecs option
You can select tests to run or skip using tags by passing --env grepTags=... value.
# enable the tests with tag "one" or "two"
--env grepTags="one two"
# enable the tests with both tags "one" and "two"
--env grepTags="one+two"
# enable the tests with "hello" in the title and tag "smoke"
--env grep=hello,grepTags=smoke
If you can pass commas in the environment variable grepTags, you can use , to separate the tags
# enable the tests with tag "one" or "two"
CYPRESS_grepTags=one,two npx cypress run
Cypress tests can have their own test config object, and when using this plugin you can put the test tags there, either as a single tag string or as an array of tags.
it('works as an array', { tags: ['config', 'some-other-tag'] }, () => {
expect(true).to.be.true
})
it('works as a string', { tags: 'config' }, () => {
expect(true).to.be.true
})
You can run both of these tests using --env grepTags=config string.
Use + to require both tags to be present
--env grepTags=@smoke+@fast
You can run tests that match one tag or another using spaces. Make sure to quote the grep string!
# run tests with tags "@slow" or "@critical" in their names
--env grepTags='@slow @critical'
You can skip running the tests with specific tag using the invert option: prefix the tag with the character -.
# do not run any tests with tag "@slow"
--env grepTags=-@slow
If you want to run all tests with tag @slow but without tag @smoke:
--env grepTags=@slow+-@smoke
Note: Inverted tag filter is not compatible with the grepFilterSpecs option
You can skip running the tests with specific tag, even if they have a tag that should run, using the not option: prefix the tag with --.
Note this is the same as appending +-<tag to never run> to each tag. May be useful with large number of tags.
If you want to run tests with tags @slow or @regression but without tag @smoke
--env grepTags='@slow @regression --@smoke'
which is equivalent to
--env grepTags='@slow+-@smoke @regression+-@smoke'
The tags are also applied to the "describe" blocks. In that case, the tests look up if any of their outer suites are enabled.
describe('block with config tag', { tags: '@smoke' }, () => {})
# run any tests in the blocks having "@smoke" tag
--env grepTags=@smoke
# skip any blocks with "@smoke" tag
--env grepTags=-@smoke
See the cypress/integration/describe-tags-spec.js file.
Note: global function describe and context are aliases and both supported by this plugin.
Sometimes you want to run only the tests without any tags, and these tests are inside the describe blocks without any tags.
$ npx cypress run --env grepUntagged=true
By default, when using grep and grepTags all specs are executed, and inside each the filters are applied. This can be very wasteful, if only a few specs contain the grep in the test titles. Thus when doing the positive grep, you can pre-filter specs using the grepFilterSpecs=true parameter.
# filter all specs first, and only run the ones with
# suite or test titles containing the string "it loads"
$ npx cypress run --env grep="it loads",grepFilterSpecs=true
# filter all specs files, only run the specs with a tag "@smoke"
$ npx cypress run --env grepTags=@smoke,grepFilterSpecs=true
Note 1: this requires installing this plugin in your project's plugin file, see the Install.
Note 2: the grepFilterSpecs option is only compatible with the positive grep and grepTags options, not with the negative (inverted) "-..." filter.
Note 3: if there are no files remaining after filtering, the plugin prints a warning and leaves all files unchanged to avoid the test runner erroring with "No specs found".
Tip: you can set this environment variable in the config file file to enable it by default and skip using the environment variable:
{
"env": {
"grepFilterSpecs": true
}
}
By default, all filtered tests are made pending using it.skip method. If you want to completely omit them, pass the environment variable grepOmitFiltered=true.
Pending filtered tests
cypress run --env grep="works 2"
Omit filtered tests
cypress run --env grep="works 2",grepOmitFiltered=true
Tip: you can set this environment variable in the config file (usually cypress.config.js) file to enable it by default and skip using the environment variable:
{
"env": {
"grepOmitFiltered": true
}
}
If you specify the grep parameters the config file, you can disable it from the command line
$ npx cypress run --env grep=,grepTags=,burn=
You can burn the filtered tests to make sure they are flake-free
npx cypress run --env grep="hello world",burn=5
You can pass the number of times to run the tests via environment name burn or grepBurn or grep-burn. Note, if a lot of tests match the grep and grep tags, a lot of tests will be burnt!
If you do not specify the "grep" or "grep tags" option, the "burn" will repeat every test.
Because the Cypress test config object type definition does not have the tags property we are using above, the TypeScript linter will show an error. Just add an ignore comment above the test:
// @ts-ignore
it('runs on deploy', { tags: 'smoke' }, () => {
...
})
This package comes with src/index.d.ts definition file that adds the property tags to the Cypress test overrides interface. Include this file in your specs or TS config settings. For example, you can load it using a reference comment
// cypress/integration/my-spec.js
/// <reference types="@cypress/grep" />
If you have tsconfig.json file, add this library to the types list
{
"compilerOptions": {
"target": "es5",
"lib": ["es5", "dom"],
"types": ["cypress", "@cypress/grep"]
},
"include": ["**/*.ts"]
}
@ as tag prefix to make the tags searchable// ✅ good practice
describe('auth', { tags: '@critical' }, () => ...)
it('works', { tags: '@smoke' }, () => ...)
it('works quickly', { tags: ['@smoke', '@fast'] }, () => ...)
// 🚨 NOT GOING TO WORK
// ERROR: treated as a single tag,
// probably want an array instead
it('works', { tags: '@smoke @fast' }, () => ...)
Grepping the tests
# run the tests by title
$ npx cypress run --env grep="works quickly"
# run all tests tagged @smoke
$ npx cypress run --env grepTags=@smoke
# run all tests except tagged @smoke
$ npx cypress run --env grepTags=-@smoke
# run all tests that have tag @fast but do not have tag @smoke
$ npx cypress run --env grepTags=@fast+-@smoke
I would run all tests by default, and grep tests from the command line. For example, I could run the smoke tests first using grep plugin, and if the smoke tests pass, then run all the tests. See the video How I organize pull request workflows by running smoke tests first and its pull request workflow file.
You can set the grep string from the DevTools Console. This plugin adds method Cypress.grep and Cypress.grepTags to set the grep strings and restart the tests
// filter tests by title substring
Cypress.grep('hello world')
// run filtered tests 100 times
Cypress.grep('hello world', null, 100)
// filter tests by tag string
// in this case will run tests with tag @smoke OR @fast
Cypress.grep(null, '@smoke @fast')
// run tests tagged @smoke AND @fast
Cypress.grep(null, '@smoke+@fast')
// run tests with title containing "hello" and tag @smoke
Cypress.grep('hello', '@smoke')
// run tests with title containing "hello" and tag @smoke 10 times
Cypress.grep('hello', '@smoke', 10)
Cypress.grep()When debugging a problem, first make sure you are using the expected version of this plugin, as some features might be only available in the later releases.
# get the @cypress/grep version using NPM
$ npm ls @cypress/grep
...
└── @cypress/grep@2.10.1
# get the @cypress/grep version using Yarn
$ yarn why @cypress/grep
...
=> Found "@cypress/grep@3.1.0"
info Has been hoisted to "@cypress/grep"
info This module exists because it's specified in "devDependencies".
...
Second, make sure you are passing the values to the plugin correctly by inspecting the "Settings" tab in the Cypress Desktop GUI screen. You should see the values you have passed in the "Config" object under the env property. For example, if I start the Test Runner with
$ npx cypress open --env grep=works,grepFilterTests=true
Then I expect to see the grep string and the "filter tests" flag in the env object.
This module uses debug to log verbose messages. You can enable the debug messages in the plugin file (runs when discovering specs to filter), and inside the browser to see how it determines which tests to run and to skip. When opening a new issue, please provide the debug logs from the plugin (if any) and from the browser.
Start Cypress with the environment variable DEBUG=@cypress/grep. You will see a few messages from this plugin in the terminal output:
$ DEBUG=@cypress/grep npx cypress run --env grep=works,grepFilterSpecs=true
@cypress/grep: tests with "works" in their names
@cypress/grep: filtering specs using "works" in the title
@cypress/grep Cypress config env object: { grep: 'works', grepFilterSpecs: true }
...
@cypress/grep found 1 spec files +5ms
@cypress/grep [ 'spec.js' ] +0ms
@cypress/grep spec file spec.js +5ms
@cypress/grep suite and test names: [ 'hello world', 'works', 'works 2 @tag1',
'works 2 @tag1 @tag2', 'works @tag2' ] +0ms
@cypress/grep found "works" in 1 specs +0ms
@cypress/grep [ 'spec.js' ] +0ms
To enable debug console messages in the browser, from the DevTools console set localStorage.debug='@cypress/grep' and run the tests again.
To see how to debug this plugin, watch the video Debug @cypress/grep Plugin.
In v2 we have separated grepping by part of the title string from tags.
v1
--env grep="one two"
The above scenario was confusing - did you want to find all tests with title containing "one two" or did you want to run tests tagged one or two?
v2
# enable the tests with string "one two" in their titles
--env grep="one two"
# enable the tests with tag "one" or "two"
--env grepTags="one two"
# enable the tests with both tags "one" and "two"
--env grepTags="one+two"
# enable the tests with "hello" in the title and tag "smoke"
--env grep=hello,grepTags=smoke
Version >= 3 of @cypress/grep only supports Cypress >= 10.
License: MIT - do anything with the code, but don't blame me if it does not work.
Support: if you find any problems with this module, email / tweet / open issue on Github.
FAQs
Filter tests using substring
The npm package @cypress/grep receives a total of 146,038 weekly downloads. As such, @cypress/grep popularity was classified as popular.
We found that @cypress/grep demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 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
Research
A malicious npm campaign is targeting Ethereum developers by impersonating Hardhat plugins and the Nomic Foundation, stealing sensitive data like private keys.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.