How do I add rspec to a project?

Like this.  Note: I did not actually write a test to prove to myself that rspec works.  This is dangerous.
How do I add capybara to a project?

Following this tutorial: http://railscasts.com/episodes/257-request-specs-and-capybara

Install the gems capybara and launchy in the gemfile.  This will allow us to run readable integration tests.

I like readable integration tests.  They make me happy because I can read them without being confused by coding syntax.
How do I set things up so that I can test if my javascript is working?

According to this railscast, like the code in here.

http://railscasts.com/episodes/257-request-specs-and-capybara
Remember to squash this into the previous commit

This was supposed to be bundled with the previous commit.
Added a gitignore to prevent logfiles from being commited with the repo

We won't have logfiles cluttering up our repo
How to we create a comprehensive testing suite into our rails app?

This suite has
  1. basic unit tests
  2. integeration tests that can test
       1. javascript
  3. UNTESTED: Selinium webpage needs to have access to the database so that changes in the database will change the views and give Selinium things to look for or click on.  I haven't built any models yet, so I dont' have anything in the datatabase to write a test for.

  This seems like an opportunity to use TDD to create a basic keyboard object so that I can test if Selinium is working.
How do I create a testing setup?

This testing setup allows me to test
 1. Unit Tests with Rspec
 2. Integration tests with capybara and selinium

 Disadvantages: it uses Selinium, which makes my tests run very slow.
  Using Selinium is the exact opposite of unit testing. Selinium is like testing that your app works by clicking on actual things on an actual webpage. Selinium is a robot that you can hire to do it really fast compared to a human, but...

  The difference between using selinium and not using selinium is the difference between putting up a tent for shelter and building a house.  A tent is a lot faster to put up than a house, and gives you the minimum you need for shelter.  A house makes you very comfortable, but takes a long time to build.

  You usually want a tent rather than a house for testing, because you are going to be setting up and tearing down this tent a LOT.

The advantage of using selinium in this way is that we can test if our javascript is working.
The disadvantage is that we're building a house every time we want to check if our app is working.
Added devise views. I also nested the keyboard resource within the User resource. I added some small markup ot the layout file to include flash warnings from Devise, as well as some semantic markup, including a header and footer. Also added 'devise' gem to gemfile.
added migrations for devise users, added model for users, added controller for users
modified devise model and controller so we could take users first and last names on registration, and also allow them to update their first and last names when they updated their account info
set up profile page as well as links to individual user profiles
user views, controller, and model finalized
added bootstrap
tweaked it so it was a fixed width layout
transfer of files
merging