Benchmark::Harness 1.12

Benchmark::Harness is a Perl module used to test Perl applications.<br /><br />SYNOPSIS<br /><br />Benchmark::Harness will invoke subroutines at specific, parametizable points during the execution of your Perl program. These subroutines may be standard Benchmark::Harness tracing routines, or routines composed by you. The setup involves just a one line addition to your test or driver program, and is easily parameterized and turned on or off from the outside.<br /><br />To activate Benchmark::Harness on your program, add to your test or driver program the following:<br /><br />use Benchmark::Harness;<br />Benchmark::Harness:new(userPsw, 'MyHarness(reportFilename, ...)', @parameters );<br /><br />userPsw is the required user authentication to make Benchmark::Harness work. After authentication, new() loads your specified sub-harness (e.g., 'Benchmark::Harness::MyHarness') and executes the initialize() method on it, giving it the parameters specified in parantheses here. reportFilename specifies how to report the results from your harness, and @parameter is a list of 'module::sub' strings, each of which specifies a point in your target program to be monitored.<br /><br />userPsw<br /><br />The first parameter must be the userid and password (in the form "userid:password"). There is no default for this, and until you make an adjustment in the Authenticate() subroutine of Benchmark::Harness, the Benchmark::Harness will not function.<br /><br />The base class will handle basic authentication in a standard manner for you, and you may override this functionality by coding your own Authenticate() subroutine in your sub-harness.<br />'MyHarness'<br /><br />The second parameter causes your harness module to be loaded (you do not need to 'use' it to have it effective). See the documentation for Benchmark::Harness::Trace for how you would write your sub-harness.<br /><br />Each sub-harness will be handed an array consisting of the parameters given in this new() statement (as in the "(userPsw,...)" illustrated above).<br />reportFilename<br /><br />Filename specifies the disposition (or not) of the output report. Note that this is given to the sub-harness to handle as it pleases; the base class Benchmark::Harness will handle it in the following manner:<br /><br />The harness report is written to a temporary file. You can get the string contained in this file with the Benchmark::Harness::old() method. The temporary file is then deleted.<br /><br />This is a convenient way to turn the harness off. Since it can be done by parameterization from the outside, it is especially adaptable to external toggling of the harness. If '0' is specified, no action is performed by Benchmark::Harness or by your sub-harness.<br /><br />If not '1' or '0', then this parameter is interpreted as a filename into which the report is written. Benchmark::Harness::old() will now return this filename rather than the content of the file. The report file will not be deleted by Benchmark::Harness::old().<br />WARNING!<br /><br />Connecting Benchmark::Harness to your Perl application can pose a serious security/privacy risk to your application and the host computer it is running on.

Requirements:	No special requirements
Platforms:	*nix, Linux
Keyword:	Authenticate,  Authentication,  Benchmarkharness,  Benchmarkharnessold,  Filename,  Handle,  Harness,  Method,  Parameter,  Parameters,  Program,  Report,  Specifies,  Subharness,  Subroutine,  Subroutines,  Temporary,  Written
Users rating:	0/10