Skip to content
User space solution for picking Cypress tests to run
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.vscode start Mar 21, 2019
__snapshots__ chore: testing fgrep Mar 22, 2019
cypress
src
test
.gitignore use fgrep and grep Mar 21, 2019
.npmrc add package lock Mar 21, 2019
README.md
circle.yml add snapshots Mar 21, 2019
cypress.json start Mar 21, 2019
grep.js
package-lock.json
package.json feat: export Mocha-like selection Mar 22, 2019

README.md

cypress-select-tests

User space solution for picking Cypress tests to run

NPM

Build status semantic-release standard renovate-app badge

Install

Assuming Cypress has been installed:

npm install --save-dev cypress-select-tests

Warning ⚠️

  • this package assumes JavaScript specs
  • this package might conflict and/or overwrite other Cypress Browserify preprocessor settings

Mocha-like selection

Mocha has --fgrep and --grep CLI arguments to select spec files and tests to run. This package provides imitation using strings. In your cypress/plugins/index.js use:

const selectTestsWithGrep = require('cypress-select-tests/grep')
module.exports = (on, config) => {
  on('file:preprocessor', selectTestsWithGrep(config))
}

Then open or run Cypress and use environment variables to pass strings to find. There are various ways to pass environment variables, here is via CLI arguments:

 ## run tests with "works" in their full titles
 $ npx cypress open --env grep=works
 ## runs only specs with "foo" in their filename
 $ npx cypress run --env fgrep=foo
 ## runs only tests with "works" from specs with "foo"
 $ npx cypress run --env fgrep=foo,grep=works
 ## runs tests with "feature A" in the title
 $ npx cypress run --env grep='feature A'

Write your own selection logic

In your cypress/plugins/index.js use this module as a file preprocessor and write your own pickTests function.

const selectTests = require('cypress-select-tests')

// return test names you want to run
const pickTests = (filename, foundTests, cypressConfig) => {
  // found tests will be names of the tests found in "filename" spec
  // it is a list of names, each name an Array of strings
  // ['suite 1', 'suite 2', ..., 'test name']

  // return [] to skip ALL tests
  // OR
  // let's only run tests with "does" in the title
  return foundTests.filter(fullTestName => fullTestName.join(' ').includes('does'))
}

module.exports = (on, config) => {
  on('file:preprocessor', selectTests(config, pickTests))
}

Using pickTests allows you to implement your own test selection logic. All tests filtered out will be shown / counted as pending.

Examples

Debugging

To see additional debugging output run

DEBUG=cypress-select-tests npx cypress open

Small print

Author: Gleb Bahmutov <gleb.bahmutov@gmail.com> © 2019

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

MIT License

Copyright (c) 2019 Gleb Bahmutov <gleb.bahmutov@gmail.com>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

You can’t perform that action at this time.