Releases: badeball/cypress-cucumber-preprocessor
v12.0.0
Breaking changes:
- A minor change to step definitions has been introduced, affecting users of Cypress v10 or higher. When upgrading to v11.0.0 of the processor, users was instructed to remove certain prefixes from their step definitions. This is no longer required and said prefixes can be re-introduced when upgrading to v12.0.0 of the preprocessor. In other words, if your configuration looks like this
{
"stepDefinitions": [
"[filepath].{js,ts}",
"cypress/support/step_definitions/**/*.{js,ts}"
]
}.. then it should now look like this (notice the addition of cypress/e2e)
{
"stepDefinitions": [
"cypress/e2e/[filepath].{js,ts}",
"cypress/support/step_definitions/**/*.{js,ts}"
]
}Note: Step definitions doesn't necessarily have to be put in cypress/e2e and alongside your feature files. They can be contained in an entirely separate directory, if desired. This fixes #748.
Other changes:
v11.5.1
v11.5.0
v11.4.0
v11.3.1
v11.3.0
v11.2.0
v11.1.0
v11.0.0
Breaking changes:
- Dropped support for Cypress v6.
Other changes:
-
Added support for Cypress v10. 🎉
-
Untitled scenario outline no longer errors, fixes #731.
-
Outputting only messages is now possible, fixes #724.
-
Allow absolute output paths, partially fixes #736.
-
Output directories are automatically created recursively, partially fixes #736.
Upgrading to Cypress v10
There's no changes to configuration options, but if your configuration looked like this pre-10
{
"stepDefinitions": [
"cypress/integration/[filepath].{js,ts}",
"cypress/support/step_definitions/**/*.{js,ts}"
]
}.. then it should look like this post-10 (notice the removal of cypress/integration)
{
"stepDefinitions": [
"[filepath].{js,ts}",
"cypress/support/step_definitions/**/*.{js,ts}"
]
}