NAME
App::TestOnTap::_Args - hidden flags
Commandline options and arguments understood for TestOnTap processing
VERSION
Version 1.001
SYNOPSIS
testontap
[ --_help ]
[
{
--_pp
|
--_pp_script <filepath>
|
--_info
|
--_ignore_dependencies
}
]
OPTIONS AND ARGUMENTS
All options can be abbreviated, as long as they are unambiguous. Option matching is case sensitive. Forcibly end option parsing using '--'.
This documents some 'hidden' flags, generally because they're somewhat particular and/or not ready for prime time...
- --_help
-
Displays usage and help with options/arguments. If given, nothing else will be done.
- --_pp or --_pp_script <path>
-
Will attempt to generate a binary using the 'pp' command from PAR::Packer. The binary gets a default name of 'testontap-<version>-<os>-<arch>'.
An existing file will not be overwritten.
By using the
--verbose
flag, pp verbosity can be raised.If you need to customize the creation of the binary, use the
--_pp_script
option to generate a Perl script. Changing the output file name can easiest be done by using '--outfile <file>', but for more advanced purposes, edit the script directly. The script should be run immediately after generation, i.e. before any config changes are made to the Perl installation, and not saved after that.When a packed binary is run, any
PERL5LIB
envvar is just dropped due to how PAR::Packer works, but if you find it is needed when running the tests, set theTESTONTAP_PERL5LIB
to the desired value and thePERL5LIB
variable will be set with that value during the running of the tests.Note that these options can not be used when you already run a binary.
- --_pp_info
-
Prints information about the context when the binary was built - the configuration (perl -V), the modules available (according to ExtUtils::Installed) and the command line used for the
pp
command.This information is embedded at the time of packing and read from those files.
Note that this option can only be used when you run a binary.
- --_ignore_dependencies
-
This will turn off the dependencies mechanism between tests - only use for debugging/testing of testontap itself.
MORE HELP
For full information on TestOnTap, see the manual, or use --manual or run perldoc App::TestOnTap to see the manual page.