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
I recently went to mark a hook as "skipped" when it performed no function so that we knew when they did/didn't run. I discovered that Cucumber marks the entire Scenario as skipped even if only the hooks are skipped, and that felt a bit strange. Is this the intended behavior?
✅ What did you expect to see?
When running a hook that reports as "skipped", I would expect the result of the Given/When/Then executions to mark the status of the scenario as success.
📦 Which tool/library version are you using?
node v22.6.0
cucumber v11.2 and v10.9
🔬 How could we reproduce it?
// testing.jsconst{ When, After }=require('@cucumber/cucumber');When('I do a thing',function(){});After(function(){return'skipped';});
# testing.featureFeature: Testing Cucumber BehaviorsScenario: TestWhen I do a thing
👓 What did you see?
I recently went to mark a hook as "skipped" when it performed no function so that we knew when they did/didn't run. I discovered that Cucumber marks the entire Scenario as
skipped
even if only the hooks are skipped, and that felt a bit strange. Is this the intended behavior?✅ What did you expect to see?
When running a hook that reports as "skipped", I would expect the result of the Given/When/Then executions to mark the status of the scenario as
success
.📦 Which tool/library version are you using?
node v22.6.0
cucumber v11.2 and v10.9
🔬 How could we reproduce it?
Output:
📚 Any additional context?
No response
The text was updated successfully, but these errors were encountered: