Add explanation on how to get setup to run the full test suite.

piotrmurach · piotrmurach · commit f657af7c19e8 · 2012-05-07T15:22:14.000+01:00
diff --git a/README.md b/README.md
@@ -351,12 +351,10 @@ end
 
 The test suite is split into two groups `live` and `mock`.
 
-The `live` tests are the ones in `features` folder and they simply exercise the GitHub API by making live requests and then being cached with VCR in directory named `features\cassettes`.
+The `live` tests are the ones in `features` folder and they simply exercise the GitHub API by making live requests and then being cached with VCR in directory named `features\cassettes`. For details on how to get setup please navigate to `features` folder.
 
 The `mock` tests are in `spec` directory and their primary concern is to test the gem internals without the hindrance of external calls.
 
-For details on how to get setup please navigate to `features` folder.
-
 ## Development
 
 Questions or problems? Please post them on the [issue tracker](https://github.com/peter-murach/github/issues). You can contribute changes by forking the project and submitting a pull request. You can ensure the tests are passing by running `bundle` and `rake`.
diff --git a/features/README.rdoc b/features/README.rdoc
@@ -1,5 +1,9 @@
 = GithubAPI
 
+== Setup
+
+Start by renaming the 'settings.yml.sample' file to 'settings.yml'. Then fill in all the information required such as authentication token etc. This should be enough to get the whole test suite run.
+
 == Running the specs and features
 
 To run the specs first run the +bundle+ command to install the necessary gems and then +rake+ command to run the specs.
