augparse(1) [centos man page]

AUGPARSE(1)							      Augeas							       AUGPARSE(1)

NAME

       augparse - execute an Augeas module

SYNOPSIS

       augparse [OPTIONS] MODULE

DESCRIPTION

       Execute an Augeas module, most commonly to evaluate the tests it contains.

OPTIONS

       -I, --include=DIR
	   Add DIR to the module loadpath. Can be given multiple times. The directories set here are searched before any directories specified in
	   the AUGEAS_LENS_LIB environment variable, and before the default directory /usr/share/augeas/lenses.

       -t, --trace
	   Print a trace of the modules that are being loaded.

       --nostdinc
	   Do not search any of the default directories for modules. When this option is set, only directories specified explicitly with -I or
	   specified in AUGEAS_LENS_LIB will be searched for modules.

       --notypecheck
	   Do not perform lens type checks. Only use this option during lens development and make sure you typecheck lenses when you are done
	   developing - you should never use a lens that hasn't been typechecked. This option is sometimes useful when you are working on unit
	   tests for a lens to speed up the time it takes to repeatedly run and fix tests.

       --version
	   Print version information and exit.

       -h  Display this help and exit

EXAMPLES

       To run the tests in lenses/tests/test_foo.aug and use modules from the directory lenses, run

	   augparse -I lenses lenses/tests/test_foo.aug

TESTS

       Tests can appear as top-level forms anywhere in a module. Generally, the tests for a module lenses/foo.aug are kept in a separate file,
       usually in lenses/tests/test_foo.aug.

       There are two different kinds of tests that Augeas can run: get and put tests. The syntax for get tests is

	   test LENS get STRING = RESULT

       which applies the get direction of the lens LENS to STRING and compares it with the given RESULT. RESULT can either be a tree literal, the
       symbol ? to print the result of applying LENS to STRING, or the symbol * to indicate that the test should produce an exception.

       The syntax for put tests is

	   test LENS put STRING after COMMANDS = RESULT

       which first applies the get direction of the lens LENS to STRING, then applies the given COMMANDS to the resulting tree, and finally
       transforms the modified tree back to a string using the put direction of LENS. The resulting string is then compared to RESULT, which can
       be a string, the symbol ? to print the result of applying LENS to STRING, or the symbol * to indicate that the test should produce an
       exception.

SEE ALSO

       Augeas project homepage <http://www.augeas.net/>

       augtool

Augeas 1.0.0							    2013-02-06							       AUGPARSE(1)

MAPITEST(1)						     OpenChange Users' Manual						       MAPITEST(1)

NAME

       mapitest - OpenChange torture test utility

SYNOPSIS

       mapitest [-?|--help] [--usage] [-f|--database=STRING] [-p|--profile=STRING]
	 [-p|--password=STRING] [--confidential] [--color] [--subunit]
	 [-o|--outfile=STRING] [--mapi-calls=STRING] [--list-all] [--no-server]
	 [--dump-data] [-d|--debuglevel=STRING]

DESCRIPTION

       mapitest  is  a	test  harness / utility used for verifying correct operation of various ExchangeRPC calls / MAPI functions provided by the
       OpenChange MAPI libraries.

       mapitest is not normally required by users, but you may be asked to provide the output of mapitest for some kinds of bug investigations.

       Note that mapitest performs a lot of transactions, including deleting folders and messages. Unless you're very familiar with  mapitest,	we
       recommend only using it with a test account.

OPTIONS

       --database

       -f     Set the path to the profile database to use

       --profile

       -p     Set  the	profile  to use. If no profile is specified, mapitest tries to retrieve the default profile in the database. If no default
	      profile has been set, mapitest returns MAPI_E_NOT_FOUND .

       --password

       -P     Specify the password for the profile to use. This can be omitted if the password is stored in the profile.

       --confidential
	      Remove any sensitive data from the report.

       --color
	      Use colors to indicate the results of each operation.

       --subunit
	      Produce output in subunit protocol format, instead of the normal text output. This disables colored output. Note	that  availability
	      of this option depends on suitable libraries being available at build time, so check availability before relying on this.

       --outfile

       -o     Redirect the output of the tests to a file. The filename must be specified as the argument to this option.

       --mapi-calls
	      Run  a specific test. The name of the test must be specified as the argument to this option. See the --list-all option to obtain the
	      name of the test.  This can be specified more than once in order to run a subset of tests.  This can also be used to run	a  "suite"
	      of tests, by appending "-ALL" to the name of the suite.

       --list-all
	      Provide a list of all test suites and test names, along with a description of the test. No tests will be run.

       --no-server
	      Only run tests that do not require a server connection. This is the default if a connection to the server cannot be established.

       --dump-data
	      Dump the hex data. This is only required for debugging or educational purposes.

       --debuglevel

       -d     Set the debug level.

EXAMPLES

       Run all tests
       mapitest

       Only run two specific tests
       mapitest --mapi-calls=NOSERVER-SROWSET --mapi-calls=OXCPRPT-GET-PROPS

       Run all the NSPI tests
       mapitest --mapi-calls=NSPI-ALL

REMARKS

       If you are using the default profile database path and have set a default profile (using mapiprofile --profile=profile_name -S ) you do not
       need to specify these parameters on the command line.

AUTHOR

       mapitest was written by Julien Kerihuel <j.kerihuel at openchange dot org> with contributions from other OpenChange developers.

       This man page was written by Brad Hards <bradh at openchange dot org>

OpenChange 2.0 QUADRANT 					    2013-01-24							       MAPITEST(1)