testing.txt in rubylexer-0.6.2 vs testing.txt in rubylexer-0.7.0

@@ -1,10 +1,12 @@
 
 Running the tests:
-the simplest thing to do is run testcode/locatetest. this will use locate to find as much ruby
-code on your system and test each specimen to see if it can be tokenized correctly (by feeding it 
-to testcode/rubylexervsruby.rb, the operation of which is outlined below under 'testing strategy').
+the simplest thing to do is run "ruby -Ilib test/code/locatetest.rb". 
+this will use locate to find as much ruby code on your system and test 
+each specimen to see if it can be tokenized correctly (by feeding it to 
+testcode/rubylexervsruby.rb, the operation of which is outlined below 
+under 'testing strategy').
 
 Interpreting the output of rubylexervsruby.rb (and locatetest):
 in rubylexervsruby, i've tried to follow the philosophy that the test program
 doesn't print anything unless there's an error. perhaps i haven't followed
 this far enough; every run of rubylexervsruby produces a little output, and 
@@ -125,6 +127,6 @@
 it is possible, however, that rubylexer is emitting as a single token things that ruby
 thinks should be 2 tokens. and in fact, this is the case with strings: ruby divides a
 string into string open, string body, and string close tokens with option interpolations,
 whereas rubylexer has just a single string token (with subtokens, if interpolations are
 present.) this difference in handling accounts in part for rubylexer's inability
-to correctly lex certain very complicated strings.
\ No newline at end of file
+to correctly lex certain very complicated strings.