We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It looks like the :binstubs => true option is ignored.
:binstubs => true
Here is the verbose output of guard:
> bin/guard -g features --verbose Guard uses GNTP to send notifications. Guard is now watching at '/Users/dnagir/proj/abc' DEBUG (17:33:51): Hook :start_begin executed for Guard::Cucumber Running all features DEBUG (17:33:51): Command execution: bundle exec cucumber --color --format pretty --no-profile --tags @focus --require /Users/dnagir/.rvm/gems/jruby-1.6.5.1/gems/guard-cucumber-0.7.4/lib/guard/cucumber/notification_formatter.rb --format Guard::Cucumber::NotificationFormatter --out /dev/null --require features features Disabling profiles...
And the config is:
guard 'cucumber', :binstubs => true, :cli => '--color --format pretty --no-profile '--tags @focus do watch(%r{^features/.+\.feature$}) watch(%r{^features/support/.+$}) { 'features' } watch(%r{^features/step_definitions/(.+)_steps\.rb$}) { |m| Dir[File.join("**/#{m[1]}.feature")][0] || 'features' } end
Using the guard from master branch and guard-cucumber (0.7.4).
Am I doing something wrong?
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
It looks like the
:binstubs => true
option is ignored.Here is the verbose output of guard:
And the config is:
Using the guard from master branch and guard-cucumber (0.7.4).
Am I doing something wrong?
The text was updated successfully, but these errors were encountered: