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
It would be nice if exceptions in a Before or After hook over the wire protocol were handled the same way as with the Ruby language implementation. Today, I get either a long, irrelevant backtrace (from the Ruby side, not the backtrace passed over the wire) or it fails silently after the Scenario line is output. I'm not sure why I get one or the other at this point.
It would be nice if exceptions in a Before or After hook over the wire protocol were handled the same way as with the Ruby language implementation. Today, I get either a long, irrelevant backtrace (from the Ruby side, not the backtrace passed over the wire) or it fails silently after the Scenario line is output. I'm not sure why I get one or the other at this point.
I've added a scenario in my fork to express the behavior I'd like: richardlawrence@4effaf1.
The text was updated successfully, but these errors were encountered: