cypress-grep
cypress-grep copied to clipboard
cypress-io
Filter tests using substring
Hi, It seems to me that cypress-grep does not work when I define test scenarios using enum like below `describe("Test1", () => { it( "Test1 successful", { tags: [TestGroup.E2E, TestGroup.SMOKE]...
This doesn't appear to be working for me i.e. it runs all the tests rather than just those with the "smoke" tag. `npx cypress run --config-file cypress-local.config.js --env cypress_host="http://www.site.com.docksal.site" --env...
The updated version of find-test-names outputs full test names, i.e. prepended with the parent suite names. This allows grepFilterSpecs to filter spec files when negative grep matches test but not...
As per the below documentation the env variables will be given in "upper snake case" while the same in the env field in config will be in camel case https://docs.cypress.io/guides/guides/environment-variables#Option-3-CYPRESS_...
./node_modules/.bin/cypress run --env grepTags="Smoke" Above command is running all of the tests.
In an effort to better maintain and enhance this official plugin, we will be moving it into the [main Cypress repo](https://github.com/cypress-io/cypress) sometime in the next few weeks. During that time,...
Correcting the error message when trying to use `cypress-grep` 3.x.x with `cypress`
Hi, I've taken the liberty to re-organize the readme. The goal was primarily to make it easier to find the relevant API faster, because not all options are available for...
I have env files for each environment (dev,qa,uat,prod) when passing "grepFilterSpecs": true in the env file grepFilterSpecs is not working. I am thinking this either a bug or I am...
Allows test suites with a variable number of tags (zero or more) to always exclude certain tags. Addresses issue #129.
