from small one page howto to huge articles all in one place
 

search text in:





Poll
Which screen resolution do you use?










poll results

Last additions:
using iotop to find disk usage hogs

using iotop to find disk usage hogs

words:

887

views:

186386

userrating:

average rating: 1.7 (102 votes) (1=very good 6=terrible)


May 25th. 2007:
Words

486

Views

250363

why adblockers are bad


Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

words:

161

views:

137545

userrating:

average rating: 1.4 (42 votes) (1=very good 6=terrible)


April, 26th. 2006:

Druckversion
You are here: manpages





GTESTER

Section: User Commands (1)
Updated:
Index Return to Main Contents
 

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)


 

Index

NAME
SYNOPSIS
DESCRIPTION
OPTIONS
SEE ALSO





Support us on Content Nation
rdf newsfeed | rss newsfeed | Atom newsfeed
- Powered by LeopardCMS - Running on Gentoo -
Copyright 2004-2020 Sascha Nitsch Unternehmensberatung GmbH
Valid XHTML1.1 : Valid CSS : buttonmaker
- Level Triple-A Conformance to Web Content Accessibility Guidelines 1.0 -
- Copyright and legal notices -
Time to create this page: 18.4 ms