Skip to content
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

why ticketee-v2 do not use cucumber like in v1? #2

Open
cmal opened this issue Mar 6, 2013 · 4 comments
Open

why ticketee-v2 do not use cucumber like in v1? #2

cmal opened this issue Mar 6, 2013 · 4 comments

Comments

@cmal
Copy link

cmal commented Mar 6, 2013

why ticketee-v2 do not use cucumber like in v1?
does v2 use RSpec do everything?
another question: when bundle install, it reports an error: Could not find capistrano-2.13.0 in any of the sources. How to fix it?
thank you for your time!

@radar
Copy link
Collaborator

radar commented Mar 6, 2013

Hi @cmal!

The second version of the book uses RSpec and Capybara rather than Cucumber because that is what the community was/is trending towards while the book is being written. It's also much easier for programmers to understand and use Capybara rather than writing steps for Cucumber which are using Capybara anyway.

I hope that answers your question :)

@radar
Copy link
Collaborator

radar commented Mar 6, 2013

Regarding capistrano problem, I don't know what's going wrong. Any chance that you have a .bundle/config file in your repository? I thik that could be causing your problem.

@cmal
Copy link
Author

cmal commented Mar 10, 2013

thank you for your answer. It saved a lot of my time.
but the capistrano problem, I cannot find a .bundle/config file in my repo.
in fact, when I ' gem install capistrano', it shows 'Successfully installed capistrano-2.14.2'.
I wonder whether it is a version problem. So can you tell me should I get my capistrano back to 2.13.0? and how ?
thank you for your time!

@cmal
Copy link
Author

cmal commented Mar 10, 2013

https://rubygems.org/gems/capistrano/versions
It shows 2.13.0 is a 'yanked' version. I don't know what 'yanked' means. Is that relavent to this problem?
thank you for your help!

@tjmcewan tjmcewan mentioned this issue Jun 5, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants