Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   31170 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

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:
	   <term>perf</term><listitem>run performance tests
	   </listitem><term>slow, thorough</term><listitem>run slow tests, or
	   repeat non-deterministic tests more often
	   </listitem><term>quick</term><listitem>do not run slow or
	   performance tests, or do extra repeats of non-deterministic tests
	   (default) </listitem><term>undefined</term><listitem>run test cases
	   that deliberately provoke checks or assertion failures, if
	   implemented (default)
	   </listitem><term>no-undefined</term><listitem>do not run test cases
	   that deliberately provoke checks or assertion failures
	   </listitem>.sp

       -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)

User Commands			  07/14/2012			    GTESTER(1)

Vote for polarhome