-
-
Notifications
You must be signed in to change notification settings - Fork 149
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
Support suite-level test configuration via Feature tags #1158
Comments
That'd be fine. I recommend that you specify the desired behavior using tests before implementing anything though, and use that to propose new behavior. |
I've create a pull request with a test showing the desired behaviour. I'd played around with implementation, as it looked like a small change, so I pushed those changes too. |
This has been fixed with v20.0.2. |
Current behavior
Suite-level configuration, eg
testIsolation
, cannot be applied using tags.Eg.
Does not work.
Desired behavior
Tags set on a
Feature
get applied to the correspondingdescribe
so that suite-level configuration can be altered.Test code to reproduce
I've created a small repository with a single feature file to demonstrate the issue https://github.com/marvelapp/suite-level-tags
In this repo when I run the test suite I see
No commands were issued in this test
for each scenario.
I see from the code that this will never work because configuration set via tags is always set on the test, ie
it
.If this feature request is reasonable I'm happy to create a pull request for it.
Versions
Checklist
cypress-cucumber-preprocessor@4.3.1
(package name has changed and it is no longer the most recent version, see #689).The text was updated successfully, but these errors were encountered: