A lot of changes to switch to the new name, might be horribly broken.

test/README

@@ -18,7 +18,7 @@ The main ideas behind the Orca test harness are as follows:
   and the expected results.  We try to keep the description of the
   tests here:
 
-  http://cvs.gnome.org/viewcvs/*checkout*/orca/docs/doc-set/orca.html#TESTINGPLAN
+  http://cvs.gnome.org/viewcvs/*checkout*/cthulhu/docs/doc-set/cthulhu.html#TESTINGPLAN
 
 * Each test is intended to be small and test for a specific feature
   of Orca and/or for a specific bug that has been been found and
@@ -52,11 +52,11 @@ PREREQUISITES:
 --------------
 
 The main prerequisite for running the tests is that you've checked the
-orca module out from the GNOME git repository.  If you want to do
+cthulhu module out from the GNOME git repository.  If you want to do
 regression testing to compare the test results with a known 'correct'
-set of results, you need to create an 'orca' user on your machine and
+set of results, you need to create an 'cthulhu' user on your machine and
 run the tests while logged in as that user.  It's best if you check
-the orca module out directly in the home directory of the user running
+the cthulhu module out directly in the home directory of the user running
 the tests.
 
 
@@ -102,7 +102,7 @@ MAIN FILES:
 
 ./results/*: The ./results directory should contain a set of
   directories that matches those in the ./keystrokes directory.
-  Under each of the ./results/* directores are *.orca files
+  Under each of the ./results/* directores are *.cthulhu files
   containing the reference speech and braille output from a
   known successful run of Orca using the associated *.keys file.
 
@@ -115,20 +115,20 @@ and leave it in its initial startup state.  For example, if you want
 to write a test for gedit, just start 'gedit' and don't do anything in
 it yet.
 
-In a separate terminal window, run orca's 'record_keystrokes.py'
+In a separate terminal window, run cthulhu's 'record_keystrokes.py'
 module and immediately give focus back to the window of the
 application you are testing.  You can run the record_keystrokes.py
 module as follows (the 'sleep 5' gives you time to put focus back on
 the app):
 
-  sleep 5; python ~/orca/src/tools/record_keystrokes.py > myfile.keys
+  sleep 5; python ~/cthulhu/src/tools/record_keystrokes.py > myfile.keys
 
 Then, interact with the application and press F12 when you are done.
 The F12 tells record_keystrokes.py to quit.  If you want to do a rough
 verification that the recorded file is OK, you can run the
 'sanity_check.py' module:
 
-  python ~/orca/src/tools/sanity_check.py < myfile.keys
+  python ~/cthulhu/src/tools/sanity_check.py < myfile.keys
 
 NOTE: You need to be somewhat careful about recording tests.  There
 are cases where some keystrokes do not make it to the AT-SPI, such as