This is a detailed tutorial showing how to set up a Rails 3 project using Devise with RSpec and Cucumber. Devise gives you ready-made authentication and user management. RSpec is a popular alternative to the Test::Unit testing framework. Cucumber is often used with RSpec for Behaviour Driven Development.
Best of all, there’s a detailed tutorial (walk-through) to show how it’s built.
You can clone this app or generate a new Rails application using this app as a template.
This is new as of April 22, 2011. Feedback from Rails developers is what makes the tutorial and example app useful. Even if you are already experienced with Devise, RSpec, and Cucumber, please work through the tutorial and offer your suggestions for improvements. You can edit the tutorial (it’s just a wiki page) or create an issue on GitHub.
To keep up to date with development of this app, follow me on Twitter:
Any issues? Please create an Issue on GitHub.
A complete walkthrough tutorial is available on the GitHub wiki:
The tutorial documents each step to follow to create the application. Every step is documented concisely, so a complete beginner can create this application without any additional knowledge. However, no explanation is offered for any of the steps, so if you are a beginner, you’re advised to look for an introduction to Rails elsewhere.
If you simply wish to modify the application for your own project, you can download the application and set it up as described below, without following the tutorial.
If you’d like to use the Mongoid ORM with the MongoDB datastore instead of ActiveRecord and a SQLite database, see the rails3-mongoid-devise example app and tutorial. Mongoid makes development quicker without schemas or migrations. The rails3-mongoid-devise example app and tutorial shows how to set up Devise and Mongoid with RSpec and Cucumber.
This is a barebones application that serves to demonstrate Devise working on Rails 3 with RSpec and Cucumber.
All you can do is visit a home page and see a list of users. With the default user’s email and password (supplied below), you can log in and view details for each user. You can customize this app as you need.
Before running this app, you need to install
- The Ruby language (version 1.8.7 or 1.9.2)
- Rails (version 3.0.7)
I recommend installing rvm, the Ruby Version Manager, to manage multiple versions of Rails.
Check that appropriate versions of Ruby and Rails are installed in your development environment:
$ ruby -v
$ rails -v
You have several options for getting the code.
If you simply wish to examine the example code, you can download the code (“clone the repository”) with the command
$ git clone git://github.com/fortuity/rails3-devise-rspec-cucumber.git
The source code is managed with Git (a version control system). You’ll need Git on your machine (install it from http://git-scm.com/).
You can use an application template to generate a new version of the example app. You’ll find an application template for this app in the fortuity/rails3-application-templates repository.
Use the command:
$ rails new APP_NAME -m https://github.com/fortuity/rails3-application-templates/raw/master/rails3-devise-rspec-cucumber-template.rb -T -J
-T -J flags to skip Test::Unit files and Prototype files.
You MUST be using Rails 3.0.4 or newer. Generating a Rails application from an “HTTPS” URL does not work in Rails 3.0.3 and earlier versions.
This creates a new Rails app (with the
APP_NAME you provide) on your computer.
The application generator template will ask you for your preferences:
- Would you like to use jQuery instead of Prototype?
- Would you like to use jQuery UI?
- Would you like to use Haml instead of ERB?
- Would you like to use RSpec instead of TestUnit?
- Would you like to use factory_girl for test fixtures with RSpec?
- Would you like to use Cucumber for your BDD?
- Would you like to use Devise for authentication?
- Would you like to set a robots.txt file to ban spiders?
The tutorial shows how a customized application template can be assembled from “recipes.” The application template was created using the rails3_devise_wizard gem which provides a convenient way to assemble a reusable application template by selecting various “recipes” for popular Rails development packages.
If you’re open sourcing the app on GitHub, please edit the README file to add a description of the app and your contact info. Changing the README is important if you’re using a clone of the example app. I’ve been mistaken (and contacted) as the author of apps that are copied from my example.
The application uses the following gems. I recommend checking for newer versions of these gems before proceeding:
- rails (check rubygems.org for the rails gem)
- devise (Check rubygems.org for the devise gem)
- rspec-rails (Check rubygems.org for the devise gem)
- database_cleaner (Check rubygems.org for the devise gem)
- factory_girl_rails (Check rubygems.org for the devise gem)
- cucumber-rails (Check rubygems.org for the devise gem)
- capybara (Check rubygems.org for the devise gem)
The app has been tested with the indicated versions. If you are able to build the app with a newer gem, please create an issue on GitHub and I will update the app.
Install the required gems on your computer:
$ bundle install
You can check which gems are installed on your computer with:
$ gem list --local
Keep in mind that you have installed these gems locally. When you deploy the app to another server, the same gems (and versions) must be available.
This app uses Devise for user management and authentication. Devise is at http://github.com/plataformatec/devise.
You can modify the configuration file for Devise if you want to use something other than the defaults:
Configure email by modifying
and setting the return email address for emails sent from the application.
You may need to set values for your mailhost in
You’ll want to set up a default user so you can easily log in to test the app. You can modify the file db/seeds.rb for your own name, email and password:
puts 'SETTING UP DEFAULT USER LOGIN' user = User.create! :name => 'First User', :email => 'firstname.lastname@example.org', :password => 'please', :password_confirmation => 'please' puts 'New user created: ' << user.name
Use the defaults or change the values for name, email, and password as you wish.
Add the default user to the database by running the command:
$ rake db:migrate
$ rake db:seed
You can check that your app runs properly by entering the command
$ rails server
To see your application in action, open a browser window and navigate to http://localhost:3000/. You should see the default user listed on the home page. When you click on the user’s name, you should be required to log in before seeing the user’s detail page.
To sign in as the default user, (unless you’ve changed it) use
- email: email@example.com
- password: please
You should delete or change the pre-configured logins before you deploy your application.
For your convenience, here are instructions for deploying your app to Heroku. Heroku provides low cost, easily configured Rails application hosting.
To deploy this app to Heroku, you must have a Heroku account. If you need to obtain one, visit http://heroku.com/ to set up an account.
Make sure the Heroku gem is in your Gemfile (check rubygems.org for the latest heroku gem):
If it’s not, add it and run
$ bundle install
to set up your gems again.
Add your public key immediately after installing the heroku gem so that you can use git to push or clone Heroku app repositories. See http://devcenter.heroku.com/articles/heroku-command for details.
Use the Heroku create command to create and name your new app.
$ heroku create _myapp_
As of 9 February 2011, bamboo-ree-1.8.7 is the default stack for new Heroku apps.
If you want to use Ruby 1.9.2, you can create your app with:
heroku create _myapp_ --stack bamboo-mri-1.9.2
You can check that everything has been added correctly by running:
$ heroku info --app myapp
If you see
Stack: bamboo-ree-1.8.7 and you want to use Ruby 1.9.2, you can migrate:
heroku stack:migrate bamboo-mri-1.9.2
Push your application to Heroku:
$ git push heroku master
Initialize your application database:
$ heroku rake db:seed
Open your Heroku site in your default web browser:
$ heroku open
If you get errors, you can troubleshoot by reviewing the log files:
$ heroku logs
Devise provides a variety of features for implementing authentication. See the Devise documentation for options.
This application provides no useful functionality apart from demonstrating Devise with RSpec and Cucumber working together on Rails 3. Add any models, controllers, and views that you need.
The application contains RSpec unit tests and Cucumber scenarios and steps. The tests are minimal and can be improved.
Please send the author a message, create an issue, or submit a pull request if you can contribute improved RSpec or Cucumber files.
After installing the application, run
rake -T to check that rake tasks for RSpec and Cucumber are available.
rake spec to run all RSpec tests.
rake cucumber (or more simply,
cucumber) to run all Cucumber scenarios and steps.
You can browse and search the Cucumber features at the Relish website.
This is the only documentation.
For a Devise introduction, Ryan Bates offers a Railscast on Devise. You can find documentation for Devise at http://github.com/plataformatec/devise. There is an active Devise mailing list and you can submit Devise issues at GitHub.
Please create an Issue on GitHub if you identify any problems or have suggestions for improvements.
If you make improvements to this application, please share with others.
Send the author a message, create an issue, or fork the project and submit a pull request.
If you add functionality to this application, create an alternative implementation, or build an application that is similar, please contact me and I’ll add a note to the README so that others can find your work.
Daniel Kehoe (http://danielkehoe.com/) implemented the application and wrote the tutorial.
Is the app useful to you? Follow me on Twitter:
and tweet some praise. I’d love to know you were helped out by what I’ve put together.
This work is a compilation and derivation from other previously released works. With the exception of various included works, which may be restricted by other licenses, the author or authors of this code dedicate any and all copyright interest in this code to the public domain. We make this dedication for the benefit of the public at large and to the detriment of our heirs and successors. We intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this code under copyright law.