-
Notifications
You must be signed in to change notification settings - Fork 71
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
Fail background skipped tests #198
Comments
@rogertorres thanks for detailed report and diving into code!
No, this definitely was overlooked.
Actually I don't think this is an issue, because you can still use I will happily review your PR in case it's possible or fix this myself. |
@ilslv This makes total sense! I submitted a minimal PR, which I tested locally. I was wondering if it would not be a good idea to add some tests and/or a tip on the book. This is something I could do, but I would then need more time/help to really understand how you organized things there. |
…#199, #198) Co-authored-by: ilslv <[email protected]>
@rogertorres fix has been released in 0.11.2 version. |
@tyranron Thank you! |
Currently, running a test with
fail_on_skipped()
does not failBackground
skipped tests. The reason is because theBackground
steps are not being mapped as the steps directly under theScenario
are:cucumber/src/writer/fail_on_skipped.rs
Lines 92 to 95 in 935602b
If that was the only thing that needed to be changed, it would be easy (spoiler: it is not); all it takes is to copy code above and replace
Scenario::Step
withScenario::Background
.It does work, but it also leads to another issue. Once we force skipped background steps to fail, we should also allow the usage of
@allow.skipped
on these steps, which is not possible because, as you clearly stated, we cannot use tags aboveBackground
.I know you guys went deep redesigning this, so I want to understand your reasoning before proposing anything or making changes locally. My questions are:
Background
tests is not available by design?Background
?Thank you!
The text was updated successfully, but these errors were encountered: