Cucumber issues when generating a new rails app.

[Osifo Anosike]

Hi,
please i'm a newbie and enthusiast of RoR. i'm presently studying a
book(rails 3 in action). I tried setting a up a new rails app: I've
created my cucumber feature. but on running rake db:migrate, it gives a
blank output. From the book i'm to expect: (in /home/user/ticketee),

also on running rake cucumber:ok, i don't get any result.
Pleas i need help and direction. Thanks

--
Posted via http://www.ruby-forum.com/.

[Андрей Большов]

What about:

rake -T

rake --version

in common rake always print out some results, try run your command with `--trace`. If you have blank output for `rake -T` and got output `rake --version` then my guess is that you have `exit` somewhere in you app(try see in rakefile)

понедельник, 21 января 2013 г., 19:01:23 UTC+4 пользователь Ruby-Forum.com User написал:

[Osifo Anosike]

"Андрей Большов" <asno...@gmail.com> wrote in post #1093053:

> What about:
> rake -T
> rake --version
>
> in common rake always print out some results, try run your command with
> `--trace`. If you have blank output for `rake -T` and got output `rake
> --version` then my guess is that you have `exit` somewhere in you
> app(try
> see in rakefile)
>
>

> , 21 2013 ., 19:01:23 UTC+4 Ruby-Forum.com
> User :


Thanks a lot! I ran with rake -t (this time from the root of my
cucumber features directory), what i got was: "rake aborted! "You have
already activated rake 10.0.3 but your gem file requires 10.0.2 run
bundle exec may resolve this.
I ran bundle exec, but still the same error. I followed the stack
trace, but could understand the line of code pointed to.

Please permit my being amateur, and thanks in anticipation for your
reply!

[Osifo Anosike]

"Андрей Большов" <asno...@gmail.com> wrote in post #1093053:

> What about:
> rake -T
> rake --version
>
> in common rake always print out some results, try run your command with
> `--trace`. If you have blank output for `rake -T` and got output `rake
> --version` then my guess is that you have `exit` somewhere in you
> app(try
> see in rakefile)
>
>

> , 21 2013 ., 19:01:23 UTC+4 Ruby-Forum.com
> User :


Thanks a lot! I ran with rake -t (this time from the root of my
cucumber features directory), what i got was: "rake aborted! "You have
already activated rake 10.0.3 but your gem file requires 10.0.2 run
bundle exec may resolve this.
I ran bundle exec, but still the same error. I followed the stack

trace, but could not understand the line of code pointed to.

Please permit my being amateur, and thanks in anticipation for your
reply!

[Craig White]

----
probably the best thing to do is start doing everything the Rails 3 way…

# from command line prompt

#install locally bundled gems in your app first
#inspects Gemfile and writes Gemfile.lock
bundle install

#prefix all rake commands with 'bundle exec' to use locally bundled gems
bundle exec rake -T
bundle exec rake db:migrate
bundle exec rake cucumber:ok

You should get the idea

Craig

[Rob Biedenharn]

On Jan 22, 2013, at 4:12 PM, Craig White wrote:
> On Jan 21, 2013, at 1:15 PM, Osifo Anosike wrote:
>> "Андрей Большов" <asno...@gmail.com> wrote in post #1093053:
>>> What about:
>>> rake -T
>>> rake --version
>>>
>>> in common rake always print out some results, try run your command with
>>> `--trace`. If you have blank output for `rake -T` and got output `rake
>>> --version` then my guess is that you have `exit` somewhere in you
>>> app(try
>>> see in rakefile)
>>>
>>>
>>> , 21 2013 ., 19:01:23 UTC+4 Ruby-Forum.com
>>> User :
>>
>>
>> Thanks a lot! I ran with rake -t (this time from the root of my
>> cucumber features directory), what i got was: "rake aborted! "You have
>> already activated rake 10.0.3 but your gem file requires 10.0.2 run
>> bundle exec may resolve this.
>> I ran bundle exec, but still the same error. I followed the stack
>> trace, but could not understand the line of code pointed to.
>>
>> Please permit my being amateur, and thanks in anticipation for your
>> reply!
> ----

> probably the best thing to do is start doing everything the Rails 3 way...

>
> # from command line prompt
>
> #install locally bundled gems in your app first
> #inspects Gemfile and writes Gemfile.lock
> bundle install
>
> #prefix all rake commands with 'bundle exec' to use locally bundled gems
> bundle exec rake -T
> bundle exec rake db:migrate
> bundle exec rake cucumber:ok
>
> You should get the idea
>
> Craig

But before you do all that typing, perhaps just put ./bin at the front of you PATH and run bundler like:

bundle install --path vendor --binstubs bin

Then those binaries for the gems will be installed to ./bin/ and you won't have to prefix everything with `bundle exec` to get the benefit of the bundled gems.

-Rob