-***7.5.6 cmake warning*** - -In the new cmake world order, you cannot use an out-of-source build as the src/condor_tests directory won't be copied or otherwise correct. You'll need to do an in-source build. Since that turns your local git repo into a mess, you'll probably want to make a copy or a new clone before doing so. This should be fixed.(There is a work around - ask bt 4/2013) - -***As of V7_3*** - -**If all you want to do is test your current work space:** -1: in src, make release -2: in src, make testbin -3: in condor_tests, make all -3: make certain that the HTCondor 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 HTCondor test suite lives in src/condor_tests @@ -41,13 +26,6 @@ ./batch_test.pl -b -To run tests concurrently you specify how many to try to keep -running as it does each directory. Do all the tests and when a directory -is being being processes start 20 if they are there and maintain that level -until tests are all running. - -./batch_test.pl -e 20 -b - To set up a test environment in condor_tests/TestingPersonalCondor and run the quick class: @@ -63,8 +41,7 @@ -a <count> Run each test this many times -t <test> Run just this test -p <pretest> Just set up the testing personal HTCondor - -e <evenly> Run the tests concurrently - -w <wrap> Wrap each test in a personal HTCondor or with -t just one + Run all the top level tests( standard way for windows ) with a pristine personal HTCondor. @@ -82,32 +59,12 @@ We wrap tests because we want to change the environment(config settings) used while this test is running without impacting the other tests which are either running now or will run yet in the main personal HTCondor. It also ensures that there will be a log directory showing only what is going on during this test. -With many tests running in the starting personal HTCondor it can be hard to see what is going on. There are two ways to get a test wrapped: - -1: Run test with batch_test.pl -d . -w -t job_core_output_van -b -2: Write the test to start a personal HTCondor and then run its test - -The following files are the most basic test which is wrapped and can be run ./batch_test.pl -d . -t wrapped_test -b. See "Adding a test" below for help in writing the actual test. Below are the pieces: - -*: wrapped_test.cmd - Submit file for the test -*: wrapped_test.run - Script run to perform the test -*: x_wrapped_test_locconfigpostsrc - The items you want to be at the end of the local config file -*: wrapped_test.pl - The core test itself with call to RunTest -*: x_param.wrapped_test - Parameter file to control personal HTCondor and which daemons to run - - -**Concurrent Testing** - -1: Under V7_2-branch ./batch_test.pl -e 30 -b means try to keep thirty running at once if there are that many in the current directory(or left to do). -2: Under V7_3.1 and newer -branch ./batch_test.pl -w -e 30 -b means try to keep thirty running at once if there are that many in the current directory(or left to do). Wrap each test in a personal HTCondor to check every test for core and ERROR. - -**Core file and ERROR detection** - -1: Under V7_2-branch None -2: Automatic and done in CondorTest for all cases but concurrent testing without wrapping tests in personal condors. Tests with personal condors are always checked as are tests run sequentially in the outer testing personal HTCondor. - +With many tests running in the starting personal HTCondor it can be hard to see what is going on. All tests are wrapped within the HKCondor perl test module. +To change the HTCondor config, wrap the test yourself. +1: Write the test to start a personal HTCondor and then run it's test +The most basic test done in a personal HTcondor is "example_personal_condor_test". **General expectations**
