closes #681

+ Edit GETTING_STARTED.md to remove references to multiple tests since
there is only one test in the suite.

+ Add RUNNING_TESTS.md, which includes instructions for running multiple
tests.

Author: Chris Brown

exercises/hamming/RUNNING_TESTS.md

@@ -0,0 +1,56 @@
+# Running Tests
+
+In order to complete this exercise, and all of the subsequent exercises, you
+will need to pass multiple tests.
+
+## Understanding Test Results
+
+After you have created and saved `hamming.rb`, run the test suite. You should
+see output like the following:
+
+    # Running:
+
+    SSSSSSESSSSSSSSS
+
+    Finished in 0.002593s, 6170.4588 runs/s, 0.0000 assertions/s.
+
+      1) Error:
+    HammingTest#test_identical_strands:
+    NameError: uninitialized constant HammingTest::Hamming
+    Did you mean?  HammingTest
+        ../hamming/hamming_test.rb:9:in `test_identical_strands'
+
+    16 runs, 0 assertions, 0 failures, 1 errors, 15 skips
+
+    You have skipped tests. Run with --verbose for details.
+
+
+The letters `SSSSSSESSSSSSSSS` show that there are sixteen tests altogether,
+that one of them has an error (`E`), and that the rest of them are skipped (all
+the `S` letters).
+
+The tests are run in randomized order, which will cause the letters to display
+in random order as well.
+
+The goal is to have all passing tests, which will show in two places:
+
+1. `SSSSSSESSSSSSSSS` will become a series dots: `................`, 
+
+2. The line at the bottom will read `16 runs, 0 assertions, 0 failures, 0
+   errors, 0 skips`.
+
+## Passing Tests
+
+Write enough code to change the Error to Failure, and finally to Passing.
+
+Open `hamming_test.rb`, and find the word "skip". All but the first test start
+with "skip", which tells Minitest to ignore the test. This is so that you don't
+have to deal with all the failures at once.
+
+To activate the next test, delete the "skip", or comment it out, and run the
+test suite again.
+
+## Wash, Rinse, Repeat
+
+Delete one "skip" at a time, and make each test pass before you move to the
+next one.

exercises/hello-world/GETTING_STARTED.md

@@ -38,20 +38,21 @@ On Windows, it will complain about:
 
 On OS X and Linux, the error will be something like:
 
+
     # Running:
 
-    ESS
+    E
 
-    Finished in 0.001539s, 2599.0903 runs/s, 0.0000 assertions/s.
+    Finished in 0.001328s, 753.0121 runs/s, 0.0000 assertions/s.
 
-    1) Error:
-    HelloWorldTest#test_no_name:
+      1) Error:
+    HelloWorldTest#test_say_hi:
     NameError: uninitialized constant HelloWorldTest::HelloWorld
-      hello-world/hello_world_test.rb:20:in `test_no_name'
-    
-    3 runs, 0 assertions, 0 failures, 1 errors, 2 skips
-    
-    You have skipped tests. Run with --verbose for details.
+    Did you mean?  HelloWorldTest
+        hello_world_test.rb:19:in `test_say_hi'
+
+    1 runs, 0 assertions, 0 failures, 1 errors, 0 skips
+
 
 Within the first test, we are referencing a constant named `HelloWorld` when
 we say `HelloWorld.hello`. When Ruby sees a capitalized name like
@@ -69,19 +70,6 @@ To fix it, open up the hello_world.rb file and add the following code:
     class HelloWorld
     end
 
-### Understanding Test Failures
-
-Whether you are on Windows, Mac OS X or Linux, you will eventually be faced with
-errors and failures that look a lot like the Mac OS X / Linux error above.
-
-The letters `ESS` show that there are three tests altogether,
-that one of them has an error (`E`), and that two of them are skipped (`SS`).
-
-The goal is to have three passing tests, which will show as three dots: `...`.
-
-The tests are run in randomized order, which will cause the letters to display
-in random order as well.
-
 ## Step 3
 
 Run the test again.
@@ -131,17 +119,6 @@ out what went wrong, and then try again.
 
 If it passes, then you're ready to move to the next step.
 
-Open the hello_world_test.rb file, and find the word "skip". All but the first test
-start with "skip", which tells Minitest to ignore the test. This is so that
-you don't have to deal with all the failures at once.
-
-To activate the next test, delete the "skip", and run the test suite again.
-
-## Wash, Rinse, Repeat
-
-Delete one "skip" at a time, and make each test pass before you move to the
-next one.
-
 ## Submit
 
 When everything is passing, you can submit your code with the following