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

Unable to get status from Scenario in Cucumber 2.0.0 #836

Closed
michael-malandra opened this issue Apr 15, 2015 · 4 comments
Closed

Unable to get status from Scenario in Cucumber 2.0.0 #836

michael-malandra opened this issue Apr 15, 2015 · 4 comments
Labels
🐛 bug Defect / Bug good first issue Good for newcomers 🚦 needs tests Needs tests

Comments

@michael-malandra
Copy link

I am unable to get the status from a scenario anymore in 2.0.0. Previously in 1.3.19, I was able to call scenario.status in my After hook to get whether a scenario passed, failed, was undefined or was skipped. In 2.0.0, I can get whether a scenario passed or failed, but I cannot get the specifics, such as if the scenario was undefined or skipped.

@mattwynne mattwynne added 🐛 bug Defect / Bug 🚦 needs tests Needs tests Regression good first issue Good for newcomers labels Apr 15, 2015
@mattwynne mattwynne added this to the 2.0 milestone Apr 15, 2015
@mattwynne
Copy link
Member

Thanks for reporting. If anyone wants to get into fixing this, I suggest starting here:

https://github.com/cucumber/cucumber/blob/master/spec/cucumber/running_test_case_spec.rb

It would probably make sense to add a status or to_sym method to all the https://github.com/cucumber/cucumber-ruby-core/blob/master/lib/cucumber/core/test/result.rb subclasses.

@mattwynne mattwynne added the Easy label Apr 15, 2015
@tiago-santos-rocket
Copy link

Hey Matt,
The same happens with scenario.source_tag_names :)

@mattwynne
Copy link
Member

Fixed by #836

@lock
Copy link

lock bot commented Oct 25, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🐛 bug Defect / Bug good first issue Good for newcomers 🚦 needs tests Needs tests
Projects
None yet
Development

No branches or pull requests

3 participants