Skip to content
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

Closed
ameduza opened this issue Jul 12, 2024 · 6 comments · Fixed by #1205
Closed

[Cypress + Cucumber] Execution commands are not grouped into Given-When-Then steps #1059

ameduza opened this issue Jul 12, 2024 · 6 comments · Fixed by #1205
Assignees
Labels
theme:cypress type:improvement Improvement or request

Comments

@ameduza
Copy link

ameduza commented Jul 12, 2024

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:

  1. Open attached project cypress-cucumber-allure.zip
  2. npm install to initialize
  3. run cypress run to run all tests and produce allure-results
  4. 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
image

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.

@jhilimirejc
Copy link

Can confirm that i am seeing the same results
├── [email protected]
├─┬ [email protected]
│ ├── [email protected]
│ └── [email protected]

@ameduza
Copy link
Author

ameduza commented Sep 30, 2024

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.

@HabibMokhtar
Copy link

We're facing the same issue as well:

  • allure-cypress: 3.0.4
  • cypress: 13.15.0
  • cypress-cucumber-preprocessor: 20.1.2

@baev
Copy link
Member

baev commented Oct 3, 2024

We're already looking into the issue and will provide the fix as soon as possible

@delatrie delatrie added the type:improvement Improvement or request label Nov 4, 2024
@baev
Copy link
Member

baev commented Dec 5, 2024

The fix is available in the [email protected]

@ameduza
Copy link
Author

ameduza commented Dec 6, 2024

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.
It was a real blocker for us to upgrade to Cypress v.13x and now we unlocked for several pending changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
theme:cypress type:improvement Improvement or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants