*:: Modify LOCAL_DIR to point to <Absolute path of personal_condor>/local.$(HOSTNAME)
 *:: Modify LOCAL_CONFIG_FILE to point to <Absolute path for personal_condor>/local.$(HOSTNAME)/condor_config.local
 
-5: Ready to run the tests!
+6: Ready to run the tests!
 {code}
 source condor.sh # condor.sh is in <personal_condor>
 
+# start the personal HTCondor, needed for some tests.
+condor_master -f
+condor_who -wait:60
+
 cd <CONDOR_SRC>/condor_tests
-./batch_test.pl -d .  -t <test name>
+./run_test.pl -d .  -t <test name>
 # for example
-# ./batch_test.pl -d .  -t job_test_scheddrotation.run
+# ./run_test.pl -d .  -t job_test_scheddrotation.run
 {endcode}
 
-Always run tests with batch_test.pl. Tests requirements are mentioned in a special file (Test_Requirements) which asks batch_test to start condor on behalf of the test, certain tests may not want to run condor or may want to change the condor's configuration file before running so they will start condor themselves. In any case, it should always be safe to run test via batch_test.pl. Also batch_test.pl only supports running single test at a time for now. To run multiple tests refer {wiki: BatLabTest}.
+Always run tests with run_test.pl. Tests requirements are mentioned in a special file (Test_Requirements) which indicates which tests need to have HTCondor already running before running the test. certain tests may not want to run condor or may want to change the condor's configuration file before running so they will start condor themselves.  At present, only the  BatLab glue knows how to run multiple tests. {wiki: BatLabTest}.