Skip to content
This repository has been archived by the owner. It is now read-only.
Go to file
This branch is 13 commits ahead, 1 commit behind vikingeducation:master.

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Test First Ruby -- RSpec 3 Edition

Set up instructions

  1. Fork this repo
  2. Clone your version of the repo to your local machine
  3. On your local machine, cd into the root folder of this repo in your terminal
  4. run bundle install to install all the gems this project needs.

Getting started with the exercises

To work through the first exercise, follow this process

  1. cd into 00_hello from the root folder of this project
  2. Run rake, to run the tests. It will fail with the following error:

  1) the hello function says hello
    Failure/Error: expect(hello).to eq("Hello!")

      undefined local variable or method `hello' for #<RSpec::ExampleGroups::TheHelloFunction:0x007fa1221408f0>
      # ./00_hello/hello_spec.rb:106:in `block (2 levels) in <top (required)>'
  1. If the test fails to run and you get a rake aborted! No Rakefile found or any other error message not like the one above ensure that your working directory (pwd to see the path) contains no spaces as this is a common mistake made by people new to Rspec.
  2. Read the failure output carefully and write the code that will make it pass
  3. Run the tests again with rake
  4. This will output that one test has passed and another test failure, write the code to make the next test pass.
  5. Continue this process until all tests pass (when they are green) you have now completed the exercise.
  6. Do this for all the exercises in this project
  7. To get hints and tips about each exercise, view the index.html file that is included in each exercise folder

Basically, this is "error-driven development"... you'll keep running tests, hitting error messages, fixing those messages, running more tests... It is meant to not only test your Ruby skills but also get you comfortable seeing big scary looking stack traces and error messages. Most of the development you do at first will be just like this. In fact, most of all development is error-driven. So get comfortable with it!


  • Don't name any of your directories with spaces in them! It will give you horribly frustrating error messages and code hates dealing with spaces. For instance:

    # BAD:
    /Documents/My Homework/ruby
    # GOOD:


This is forked from, its original creator.


a basic ruby class generated from test-first-teaching



No releases published


No packages published
You can’t perform that action at this time.