qpid-python-test(1) [debian man page]

qpid-python-test(1)						   User Commands					       qpid-python-test(1)

NAME

       qpid-python-test - run tests of the python QPID library for a broker

SYNOPSIS

       qpid-python-test [options] PATTERN ...

DESCRIPTION

       Run tests matching the specified PATTERNs.

OPTIONS

       -h, --help
	      show this help message and exit

       -l, --list
	      list tests instead of executing them

       -b BROKER, --broker=BROKER
	      run tests against BROKER (default localhost)

       -f FILE, --log-file=FILE
	      log output to FILE

       -v LEVEL, --log-level=LEVEL
	      only display log messages of LEVEL or higher severity: DEBUG, WARN, ERROR (default WARN)

       -c CATEGORY, --log-category=CATEGORY
	      log only categories matching CATEGORY pattern

       -m MODULES, --module=MODULES
	      add module to test search path

       -i IGNORE, --ignore=IGNORE
	      ignore tests matching IGNORE pattern

       -I IFILE, --ignore-file=IFILE
	      ignore tests matching patterns in IFILE

       -H, --halt-on-error
	      halt if an error is encountered

       -t, --time
	      report timing information on test run

       -D DEFINE, --define=DEFINE
	      define test parameters

SEE ALSO

       For more information on qpid-python-test please check the QPID wiki at http://qpid.apache.org.

Apache QPID							   October 2011 					       qpid-python-test(1)

GTESTER(1)							   User Commands							GTESTER(1)

NAME

       gtester - test running utility

SYNOPSIS

       gtester [OPTION...] [testprogram]

DESCRIPTION

       gtester is a utility to run unit tests that have been written using the GLib test framework.

       When called with the -o option, gtester writes an XML report of the test results, which can be converted into HTML using the gtester-report
       utility.

OPTIONS

       -h, --help
	   print help and exit

       -v, --version
	   print version information and exit

       --g-fatal-warnings
	   make warnings fatal

       -k, --keep-going
	   continue running after tests failed

       -l
	   list paths of available test cases

       -m=MODE
	   run test cases in MODE, which can be one of:

	   perf
	       run performance tests

	   slow, thorough
	       run slow tests, or repeat non-deterministic tests more often

	   quick
	       do not run slow or performance tests, or do extra repeats of non-deterministic tests (default)

	   undefined
	       run test cases that deliberately provoke checks or assertion failures, if implemented (default)

	   no-undefined
	       do not run test cases that deliberately provoke checks or assertion failures

       -p=TESTPATH
	   only run test cases matching TESTPATH

       -s=TESTPATH
	   skip test cases matching TESTPATH

       --seed=SEEDSTRING
	   run all test cases with random number seed SEEDSTRING

       -o=LOGFILE
	   write the test log to LOGFILE

       -q, --quiet
	   suppress per test binary output

       --verbose
	   report success per testcase

SEE ALSO

       gtester-report(1)

GLib																	GTESTER(1)