![]() ![]() Remove a couple of gems we aren't going to use The exact versions are in Gemfile.lock anyway, and if at some point aīundle update breaks something we can always lock versions of specific # Access an IRB console on exception pages or by using in views # Call 'byebug' anywhere in the code to stop execution and get a debugger console # Use ActiveModel has_secure_password -# gem 'bcrypt', '~> 3.1.7' -# Use Unicorn as the app server -# gem 'unicorn' -# Use Capistrano for deployment -# gem 'capistrano-rails', group: :development + gem 'sqlite3' + gem 'turbolinks' + gem 'uglifier', '>= 1.3.0' ![]() ![]() # bundle exec rake doc:rails generates the API under doc/api. Read more: -gem 'turbolinks' -# Build JSON APIs with ease. # See for more supported runtimes -# gem 'therubyracer', platforms: :ruby -# Use jquery as the JavaScript library -gem 'jquery-rails' -# Turbolinks makes following links in your web application faster. # Bundle edge Rails instead: gem 'rails', github: 'rails/rails' -gem 'rails', '4.2.0' -# Use sqlite3 as the database for Active Record -gem 'sqlite3' -# Use SCSS for stylesheets -gem 'sass-rails', '~> 5.0' -# Use Uglifier as compressor for JavaScript assets -gem 'uglifier', '>= 1.3.0' -# Use CoffeeScript for. In a real project, some or all of the following might + be useful: + + * () for building test + data + * () for more realistic test values + * () to describe your site + using the () + pattern + * () to test time-dependent + code + * () to use + capybara on pages that use javascript + * () + to automatically open a screenshot of the current page when a test fails + + To keep things simple, we're not using any additional testing tools apart from + RSpec and Cucumber (apart from Database Cleaner and Capybara, which Cucumber + depends on by default). With the command(s) listed in the commit message. Where files were changedīy running a command rather than manually, that step will be a separate commit, See full commit messages for step-by-step description. + Created for a demo of TDD with (Rails), using + (RSpec) and (Cucumber). Created for a demo of TDD with Rails, using RSpec and Cucumber. Please feel free to use a different markup language if you do not plan to run -rake doc:app. Things you may want to cover: -* Ruby version -* System dependencies -* Configuration -* Database creation -* Database initialization -* How to run the test suite -* Services (job queues, cache servers, search engines, etc.) -* Deployment instructions -*. README.rdoc -= README -This README would normally document whatever steps are necessary to get the -application up and running. Where files were changed + by running a command rather than manually, that step will be a separate commit, + with the command(s) listed in the commit message. + + See full commit messages for step-by-step description. README.md + # Sample "to-do" Rails app + + Created for a demo of TDD with Rails, using RSpec and Cucumber. Reload it when changing certain things, leading to confusing test Sometimes it doesn't quite work as expected, or you forget you need to Not to install spring (a preloader to speed up test runs) because I told it not to install test-unit as we'll be using rspec instead, and Rails new todo-rails rails -skip-spring -skip-test-unit In the unlikely event that anyone wants to scroll through the whole history of the TDD demo Rails app I did the other day, I wrote a little script to munge it all into one page. ![]()
0 Comments
Leave a Reply. |