forked from netzpirat/guard-cucumber
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Cucumber task fails in notification routine #22
Comments
This, situation can be fixed with adding before_background hook in
But I don't sure if it's the best one. |
e2
added a commit
that referenced
this issue
Mar 8, 2015
handle background scenario failures [fix #22]
Thank you very much for such a detailed report (I really appreciate it!) - and for the repo (I would've never guessed it was because of a failing background scenario). I've released 1.5.4 - let me know if you have any other issues. |
Thank you too for your contribution. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To reproduce:
I have a following error output.
Arguments of
self.notify(msg, options = {})
in/home/user/.gem/ruby/2.0.0/gems/guard-compat-1.2.1/lib/guard/compat/plugin.rb
:a regular user "Jack"
is background section step.The text was updated successfully, but these errors were encountered: