You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
run cypress run to run all tests and produce allure-results
generate AllureReport and open test result
Expected 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:
Can confirm that i am seeing the same results
├── allure-commandline@2.30.0
├─┬ allure-cypress@3.0.0-beta.12
│ ├── allure-js-commons@3.0.0-beta.12
│ └── cypress@13.6.1
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).
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: