{section: Requirements}

*: Install Cygwin + Cygwin Perl module
*: Install Active-State Perl
*: Install HTCondor


{section: Preparing for testing}

The easiest way to get an ititial Windows HTCondor test environment
is to install the HTCondor msi. Take all the defaults and when you get
to where jobs run, allow them to run unimpeeded on the current system.
(After you have a test machine set up, you can replace the binaries with ones
from the zip file release for HTCondor)

You will find it helpful to place these 3 lines in c:condor/condor_config.local

{code}
CONDOR_HOST = 127.0.0.1
NETWORK_INTERFACE = 127.0.0.1
DAEMON_LIST = MASTER STARTD KBDD COLLECTOR NEGOTIATOR SCHEDD
{endcode}

{section: Testing}

{code}
Add to the system PATH environment variable the location of the HTCondor binaries
Secure the HTCondor source tar ball and extract it
Bring down to a testing location of your choice:
   condor_examples
   condor_scripts
   condor_tests
Copy *.pm and batch_test.pl from condor_scripts to condor_tests
{endcode}

From a Cygwin command-line type:

{code}
cd c:/condor
chmod go+rX bin
cd bin
chmod go+rX *
cd (into condor_tests, where ever you placed it)
./batch_test.pl -d . -b
{endcode}

{section: Results}

{code}
249 successful, 34 failed
{endcode}

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


Or, to run a single test:

  ./batch_test.pl -d . -b -t cmd_q_shows-name

Where =cmd_q_shows-name= can be any of the tests in the test suite.  As a final note, if you are planning on running the tests several times, you will need to delete the =TestingPersonalCondor= directory between test runs:

  rm -rf TestingPersonalCondor


That's about as simple as it gets; although it is possible to save exporting the =NMI_PLATFORM= and =PATH= each time.  This can be accomplished by adding them to the environment in a persistent manner; either by cygwin startup scripts or changing the Windows environment.  The latter will require a new instance of the cygwin terminal for the variables to be present.