{section:General}

batch_test.pl is the means by which the test suite is run. It can be told to start up its own personal HTCondor and use that for testing. The tests ran by batch_test.pl may also start their own personal Condors.

1: Build, install and configure your code from HTCondor source tar ball:
{code}
extract tar ball
cd into source tree(eg condor-7.9.4)
(You must have cmake)
./configure_uw
make install
make tests
cd src
cd condor_tests
export PATH=$releasedirLoc/bin:$releasedirLoc/sbin:$PATH
./batch_test.pl -b -c
{endcode}

2: Testing from the GIT repository, out of tree/out of repository:
{code}
ma/p/condor/workspaces/bt/GIT/CONDOR_SRC/configure_uw /p/condor/workspaces/bt/GIT/CONDOR_SRC
make install
make tests
cd src
cp -r /p/condor/workspaces/bt/GIT/CONDOR_SRC/src/condor_examples .
cp -r condor_tests condor_tests.built
cp -r /p/condor/workspaces/bt/GIT/CONDOR_SRC/src/condor_tests .
cd condor_tests
export PATH=$releasedirLoc/bin:$releasedirLoc/sbin:$PATH
./batch_test.pl -b -cke a directory to build and test in, cd there
{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}
$ rm -fr TestingPersonalCondor
{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}

See #1124 for tickets associated with improving tests.

*:Parallel tests are unlikely to work.  A number of tests depend on the output from other tests.  Furthermore, some tests assume no competition and may reuse files or directories.
*:Re-running tests is unlikely to work.  Tests leave a lot of garbage behind that causes problems when they run again. Solution: x_makeclean.pl or "make resubmit" might clean things up enough. (#1153 is unfinished work designed to help with this.)