jonleighton / spring-commands-cucumber Goto Github PK

This is a regression caused by #4. spring cucumber runs in test mode as expected, but spring cucumber features/foo.feature runs in development mode. This happens because args contains a path rather than an environment variable, which confuses the matcher and returns nil for the environment. I'm working on a pull request.

http://rubygems.org/gems/spring-commands-cucumber

• It's still showing 1.0.1. Is this gem upgraded to 1.1?

I'm running a Rails 4 app, configured with Spring. I installed spring-commands-cucumber 1.0.1 and did: spring binstub --all. When I run bin/cucumber, I get the following error message:

Version: 1.1.2

Usage: spring COMMAND [ARGS]

Commands for spring itself:

  binstub         Generate spring based binstubs. Use --all to generate a binstub for all known commands.
  help            Print available commands.
  status          Show current status.
  stop            Stop all spring processes for this project.

Commands for your application:

  cucumber        Runs the cucumber command
  rails           Run a rails command. The following sub commands will use spring: console, runner, generate, destroy.
  rake            Runs the rake command
  rspec           Runs the rspec command
No such file or directory - cucumber. Please create a cucumber directory to get started. (Errno::ENOENT)

I thought feature files go in the "features" directory, not the cucumber directory.

While using guard/cucumber and zeus, features ran fast! (on an older project)

When using guard/cucumber and spring (on a new project) - running features is slow. Painfully slow. Should that be the case? Shouldn't we see features running about as fast as rspec tests?

Hi,

I might be missing something here, but I'm under the impression that the bin/cucumber command will always run in the test environment. At work we use different environments for rspec and cucumber since that enables us to run the specs and cukes alongside without them hitting the same database.
I monkey patched my way out of the problem by overriding the env method in Spring::Commands::Cucumber and having it return the string I need.
I would have expected to be able to pass a RAILS_ENV='foo' to the command, since that seems to be the convention if one needs to override the default rails env.
Any chance of that being implemented in the future?

Thanks in advance