You can pass additional arguments to condor_nmi_submit to alter the test configuration
*: =--append-config-dir=<dir>= Copy =<dir>/testconfigappend= into the condor_tests directory before running the tests. The test glue will then append this file to the base condor_config produced by condor_install, and before running any of the tests. Use this to make a global config change, such as turning on IPV6
+
+*If you want to run just a few tests, you create a file in Metronome accepted syntax and name it "testoverride". This file is placed in condor_tests in your workspace.*
+Here is a sample:
+
+{code}
+JOB job_basic_suspend_continue_test-1
+JOB job_concurrency_limits-1
+{endcode}
+
+If the build you want to test was made from a git tag, you can submit the tests using the same tag:
+
+{code}
+/home/cndrauto/condor/nmi_tools/condor_nmi_submit --test --buildid=209846 \
+--tag=BUILD-trunk-2010-1-13 --module=UNUSED --git --platforms=all \
+--submit-xtests
+{endcode}
+
+If the build you want to test was a workspace build, you can submit the tests using the same workspace. Run this from the =nmi_tools= directory of your workspace:
+
+{code}
+./condor_nmi_submit --test --buildid=209633 --git --platforms=all \
+--workspace=.. --submit-xtests
+{endcode}
+
+You can restrict the set of platforms tested by giving a comma-separated list for the =--platforms= option. If you don't want any cross-platform tests, you can use =--nosubmit-xtests=.
+
+The blacklist a particular host, add something like this to the condor_nmi_submit line:
+
+{code}
+--append 'append_requirements=Machine!="nmi-0102.batlab.cs.wisc.edu"'
+{endcode}
