*This was copied from MemoryProfiling. MemoryProfiling should be updated to not duplicate information.*
-batch_test.pl is the means by which the test suite is run. It can be told to start up its own person condor and use that for testing. The tests ran by batch_test.pl may also start their own personal condors.
+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.
-After the test suite codes are built (make tests), cd into condor_tests/.
+First, make sure the tests are built:
+{code}
+$ make tests
+{endcode}
+
+Then, invoke batch_test.pl. We tell batch test to start up its own personal condors 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.
-We'll invoke batch_test.pl. We tell batch test to start up its own personal condors 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_scripts
+$ ./batch_test.pl -b -c
+{endcode}
+{subsubsection: Running the tests again}
+Running the test suite leaves files and directories in the =src/condor_tests= directory that prevent the tests from running again. To solve this:
{code}
-make tests
-cd condor_tests
-./batch_test.pl -b -c
+$ rm -fr ../condor_tests/TestingPersonalCondor
{endcode}
-Then, in the same directory as the pile of tests.* files, run this script, which will collate the tests.* files associated with Condor daemons and tools into directories.
{section: Warnings, Problems, and Workarounds}
See #1124 for tickets associated with improving tests.
*: You can't currently (2011-03-17) do out-of-source tests. You'll need to build and test inside of your repository.
-*:: Correlary: this will make will your repository with lots of new files Git will complain about. Solution: Make a copy of your repository before doing tests.
+*:: Corollary: this will make will your repository with lots of new files Git will complain about. Solution: Make a copy of your repository before doing tests.
*:: Several tests do "chmod -R 777 ." on the testing directory. This needs to be fixed as it's insecure and it angers Git (which sees the permission change as something to be committed). This needs to be fixed (#1978). In the meanwhile: Make a copy of your repository before doing tests.
*:: Several tests rewrite files in place, making them appear like they have changes that you should check in. Checking them in would be very wrong. This needs to be fixed (#1983). IN the meanwhile: Make a copy of your repository before doing tests.
*:::You might be able to fix the permissions with: {code}
