-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Cypress + Cucumber] Execution commands are not grouped into Given-When-Then steps #1059
Comments
Can confirm that i am seeing the same results |
Hey guys (@baev ), do you have any update on this? To be honest, this is a blocker for us to switch to you plugin implementation from the shelex/cypress-allure-plugin (with that one we also blocked to upgrade to Cypress v13.x b/c of the known issue). So we were really relying on your implementation. |
We're facing the same issue as well:
|
We're already looking into the issue and will provide the fix as soon as possible |
The fix is available in the [email protected] |
Thanks a lot, guys! Really appreciate for your efforts! Already tested in our project. From what I see you even group steps a bit better than previous plugin, that we used. |
Describe the bug
Execution commands are not grouped into Given-When-Then steps
Project structure: Cypress (latest) + @badeball/cypress-cucumber-preprocessor (latest )+ allure-cypress (latest: 3.0.0-beta.6)
To Reproduce
Steps to reproduce the behavior:
npm install
to initializecypress run
to run all tests and produce allure-resultsExpected behavior
Scenario commands are grouped as per Given-When-Then steps like it was in a previous Cypress-Allure adapter (@shelex/cypress-allure-plugin).
Screenshots

Additional context
I do understand that I can wrap commands into allure.step() but this doesn't make any sense in case of Cucumber. GWT steps are already containers for the commands.
The text was updated successfully, but these errors were encountered: