HTCondorWiki: Testing Condor On Unix

 $ rm -fr TestingPersonalCondor
 {endcode}
 
+{subsection: Stress testing in batch_test.pl}
+
+Sometimes a test will run in build workspace but not in the batlab. The
+batlab runs multiple tests at once and thus responsiveness  to individual tests
+is less predictable. One way to duplicate this is to run multiple tests at once
+within batch_test.pl.
+{code}
+batch_test.pl watches the list "list_quick" when you do not use "-t testname".
+{endcode}
+
+Assuming you can run multiple copies of the test which fails intermittenly
+at the same time, you can run as many as you want at once. Note however that
+some names might be used the same so the best best is to run another test
+as the load and one of the test you are working to fix.
+In this example I want to stress test job_dagman_fullremove for issues
+relating to runCondorTool getting the queries we want.
+
+Fill list_quick with:
+
+{code}
+job_dagman_fullremovejob_basic_kill
+job_basic_kill
+job_basic_kill
+job_basic_kill
+{endcode}
+
+The following command will start job_dagman_fullremove and then 3 job_basic_kill and they will all run at once.
+
+{code}
+./batch_test.pl -b -d .
+{endcode}
+
 The test suite is prone to leaving HTCondor daemons, especially if you interrupt the tests.  After running tests, check for unexpected condor_masters running and kill them.
 
 {section: Warnings, Problems, and Workarounds}