-
Notifications
You must be signed in to change notification settings - Fork 16
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
Comments
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 :) |
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. |
thank you for your answer. It saved a lot of my time. |
https://rubygems.org/gems/capistrano/versions |
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!
The text was updated successfully, but these errors were encountered: