HTCondorWiki: Testing Condor On Unix

 
 batch_test.pl is the means by which the test suite is run. It can be told to start up its own personal Condor and use that for testing. The tests ran by batch_test.pl may also start their own personal Condors.
 
-First, make sure the tests are built:
+1: Build, install and configure your code:
 {code}
-$ make tests
+make install
+pushd release_dir
+./condor_install --make-personal-condor
+source condor.csh
+popd
 {endcode}
 
-Then, invoke batch_test.pl. We tell batch_test.pl to start up its own personal Condor and clean up everything when it is done. We don't ask it to run tests in parallel since there likely are race conditions in the tests over that behavior.
+2: Make sure the tests are built:
+{code}
+make tests
+{endcode}
+
+3: Invoke batch_test.pl. We tell batch_test.pl to start up its own personal Condor and clean up everything when it is done. We don't ask it to run tests in parallel since there likely are race conditions in the tests over that behavior.
 
 {code}
-$ cd src/condor_tests
-$ ../condor_scripts/batch_test.pl -b -c
+cd src/condor_tests
+./batch_test.pl -b -c
 {endcode}
 
 {subsubsection: Running the tests again}
@@ -20,6 +29,7 @@
 $ rm -fr TestingPersonalCondor
 {endcode}
 
+The test suite is prone to leading Condor daemons, especially if you interrupt the tests.  After running tests, check for unexpected condor_masters running and kill them.
 
 {section: Warnings, Problems, and Workarounds}