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

HTML report shows as Unknown for a scenario using @skip tag #1041

Open
3 tasks
ijaved opened this issue Jun 19, 2023 · 3 comments
Open
3 tasks

HTML report shows as Unknown for a scenario using @skip tag #1041

ijaved opened this issue Jun 19, 2023 · 3 comments
Labels

Comments

@ijaved
Copy link

ijaved commented Jun 19, 2023

Current behavior

As per Smart tagging in: https://github.com/badeball/cypress-cucumber-preprocessor/blob/master/docs/tags.md

Scenario with @skip shows as as Unknown in HTML report.
image

Command line also shows the scenario as Pending but should be Skipped
image

Desired behavior

Scenarios with @skip tag should show as Skipped in the HTML report and on command line when tests have run

Test code to reproduce

Run Skipped report as detailed in: https://github.com/ijaved/cypress-cucumber-preprocessor-reporting-example/blob/main/README.md

Versions

  • Cypress version: 12.14.0:
  • Preprocessor version: 18.0.1:
  • Node version: 16.16.0:

Checklist

  • I've read the FAQ.
  • I've read instructions for logging issues.
  • I'm not using cypress-cucumber-preprocessor@4.3.1 (package name has changed and it is no longer the most recent version, see #689).
@badeball
Copy link
Owner

Command line also shows the scenario as Pending but should be Skipped

No, this is part of Cypress nomenclature outside of my control, EG. discussed here.

As far as the HTML report go - you're right, skipping isn't handled gracefully in terms of reporting. This includes returning "skipped" from hooks & steps, as well as any tag filtering in general.

For future reference, skipping steps in cucumber-js is partially described here and then there's some undescribed functionality.

@badeball badeball added the bug label Jun 19, 2023
@badeball
Copy link
Owner

This will likely depend on the existence of a test:after:run event, as described here. The referenced MR never made it into mainline it seems, despite the completion status.

I've tried to inquiry about its status, but given my history with Cypress so far, I assume it's never going to happen.

@badeball
Copy link
Owner

badeball commented Jul 9, 2023

This can be tracked here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants