3: make certain that the condor binaries you want to test are on your path, e.g. set path=(../release_dir/bin ../release_dir/sbin $path) 4: in condor_tests, ./batch_test.pl -b +_This will run the binaries in your path configured with samples generic configs from condor_examples with slight changes added to the end of the condor_config.local file_ +**About the test suite** The condor test suite lives in src/condor_tests There's no toplevel Makefile (src/Imakefile) rule that builds and runs all -of this. - -To build the test suite, go -cd src/condor_tests -make all +of this.To build and run the test suite see section above. We will get into variations later. The Imake rules know on each platform what compilers exist. For each compiler it finds on a platform, it creates a new directory underneath condor_tests that is the name of that compiler, and creates basically a symlink and copy image of everything else in condor_tests for that compiler. Then it goes through each compiler subdirectory and builds each test with that compiler, usually with the syscall library and a vanilla version of that test. Last it does any building of non-Standard Universe test in the top level. @@ -38,8 +36,6 @@ ./batch_test.pl -b -READ the README files! The naming is supposed to be concise by rules in them. This helps everyone understand what the test is doing. Additionally understand classes! The default class run by batch_test.pl is list_quick. On windows the default list of tests run comes from the file Windows_list. - The above run is setting up a test environment in condor_tests/TestingPersonalCondor running the quick class: @@ -107,6 +103,9 @@ in it's stdout a line that looks like FAILURE (failure reason) +**Adding a new test** + +READ the README files! The naming is supposed to be concise by rules in them. This helps everyone understand what the test is doing. Additionally understand classes! The default class run by batch_test.pl is list_quick. On windows the default list of tests run comes from the file Windows_list. To add a new test to the test suite, you have to do three steps: 1. Write the code for the test program itself @@ -201,14 +200,14 @@ There are many examples to look at in src/condor_tests/Imakefile. We also have a perl module called CondorPersonal.pm which allows us to setup tests which require a modified environment so as to not change the environment of the personal condor running all of the tests. It allows us to emulate most pool configurations. Look at the job_flocking_to, job_condorc_ab_van and cmd_status_shows-avail for more complicated examples. -Setting up for testing on windows +**Setting up for testing on windows** -* Install windows msi -* Add path to condor binaries(bin and sbin) to PATH env variable -* Add NMI_PLATFORM = x86_winnt_5.1 env variable -* Install cygwin with cygwin perl -* Install Active perl -* Bring down sources and move condor_examples, condor_scripts and condor_tests to c:\ -* Cp *.pm and batch_test.pl from condor_scripts to condor_tests -* Cd to condor_tests -* ./batch_test.pl --no-error -d . -b +*: Install windows msi +*: Add path to condor binaries(bin and sbin) to PATH env variable +*: Add NMI_PLATFORM = x86_winnt_5.1 env variable +*: Install cygwin with cygwin perl +*: Install Active perl +*: Bring down sources and move condor_examples, condor_scripts and condor_tests to c:\ +*: Cp *.pm and batch_test.pl from condor_scripts to condor_tests +*: Cd to condor_tests +*: ./batch_test.pl --no-error -d . -b
