Page History

Turn Off History

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: 
    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  ( or a single test: ./batch_test.pl -d . -b -t cmd_q_shows-name)

  2. Testing from the GIT repository, out of tree/out of repository: 
    make a directory to build and test in, cd there
/{repo}/CONDOR_SRC/configure_uw /{repo}/GIT/CONDOR_SRC
make install
make tests
cd src
cp -r /{repo}/CONDOR_SRC/src/condor_examples .
cp -r condor_tests condor_tests.built
cp -r /{repo}/CONDOR_SRC/src/condor_tests .
cd condor_tests
export PATH=$releasedirLoc/bin:$releasedirLoc/sbin:$PATH
./batch_test.pl -b -c  ( or a single test: ./batch_test.pl -d . -b -t cmd_q_shows-name)

  3. Results after batch_test.pl completes: 
    249 successful, 34 failed

Additionally the file failed_tests will contain the list of tests which had a non-zero return code meaning they failed. The file successful_tests will list the passing tests which had a return value of zero

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: 
$ rm -fr TestingPersonalCondor

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.

Warnings, Problems, and Workarounds

See #1124 for tickets associated with improving tests.