Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

webinject(3pm) [debian man page]

Webinject(3pm)						User Contributed Perl Documentation					    Webinject(3pm)

NAME
Webinject - Perl Module for testing web services SYNOPSIS
use Webinject; my $webinject = Webinject->new(); $webinject->engine(); DESCRIPTION
WebInject is a free tool for automated testing of web applications and web services. It can be used to test individual system components that have HTTP interfaces (JSP, ASP, CGI, PHP, AJAX, Servlets, HTML Forms, XML/SOAP Web Services, REST, etc), and can be used as a test harness to create a suite of [HTTP level] automated functional, acceptance, and regression tests. A test harness allows you to run many test cases and collect/report your results. WebInject offers real-time results display and may also be used for monitoring system response times. CONSTRUCTOR
new ( [ARGS] ) Creates an "Webinject" object. reporttype possible values are 'standard', 'nagios', 'nagios2', 'mrtg' or 'external:' nooutput suppress all output to STDOUT, create only logilfes break_on_errors stop after the first testcase fails, otherwise Webinject would go on and execute all tests regardless of the previous case. timeout Default timeout is 180seconds. Timeout starts again for every testcase. useragent Set the useragent used in HTTP requests. Default is 'Webinject'. max_redirect Set maximum number of HTTP redirects. Default is 0. proxy Sets a proxy which is then used for http and https requests. output_dir Output directory where all logfiles will go to. Defaults to current directory. globalhttplog Can be 'yes' or 'onfail'. Will log the http request and response to a http.log file. httpauth Provides credentials for webserver authentications. The format is: ['servername', 'portnumber', 'realm-name', 'username', 'password'] baseurl the value can be used as {BASEURL} in the test cases baseurl1 the value can be used as {BASEURL1} in the test cases baseurl2 the value can be used as {BASEURL2} in the test cases standaloneplot can be "on" or "off". Default is off. Create gnuplot graphs when enabled. graphtype Defaults to 'lines' gnuplot Defines the path to your gnuplot binary. METHODS
engine start the engine of webinject EXAMPLES
example test case <testcases> <case id = "1" description1 = "Sample Test Case" method = "get" url = "{BASEURL}/test.jsp" verifypositive = "All tests succeded" warning = "5" critical = "15" label = "testpage" errormessage = "got error: {PARSERESPONSE}" /> </testcases> detailed description about the syntax of testcases can be found on the Webinject homepage. SEE ALSO
For more information about webinject visit http://www.webinject.org AUTHOR
Corey Goldberg, <corey@goldb.org> Sven Nierlein, <nierlein@cpan.org> COPYRIGHT AND LICENSE
Copyright (C) 2010 by Sven Nierlein Copyright (C) 2004-2006 by Corey Goldberg This library is free software; you can redistribute it under the GPL2 license. perl v5.14.2 2012-05-12 Webinject(3pm)

Check Out this Related Man Page

Test::NeedsDisplay(3pm) 				User Contributed Perl Documentation				   Test::NeedsDisplay(3pm)

NAME
Test::NeedsDisplay - Ensure that tests needing a display have one SYNOPSIS
In your Makefile.PL... use inc::Module::Install; # ... or whatever else you use # Check for a display use Test::NeedsDisplay; # ... your Makefile.PL content as normal And again in each test script that loads Wx #!/usr/bin/perl use strict; use Test::NeedsDisplay; # Test content as normal... DESCRIPTION
When testing GUI applications, sometimes applications or modules absolutely insist on a display, even just to load a module without actually showing any objects. Regardless, this makes GUI applications pretty much impossible to build and test on headless or automated systems. And it fails to the point of not even running the Makefile.PL script because a dependency needs a display so it can be loaded to find a version. In these situations, what is needed is a fake display. The "Test::NeedsDisplay" module will search around and try to find a way to load some sort of display that can be used for the testing. Strategies for Finding a Display At this time, only a single method is used (and a very simple one). Debian Linux has a script called "xvfb-run" which is a wrapper for the "xvfb", a virtual X server which uses the linux frame buffer. When loaded without a viable display, the module will re-exec the same script using something like (for example) "xvfb-run test.t". As such, it should be loaded as early as possible, before anything has a chance to change script parameters. These params will be resent through to the script again. METHODS
There are no methods. You simply use the module as early as possible, probably right after "use strict;" and make sure to load it with only default params. Specifically, need must always load it before you set the test plan, otherwise the test script will report two plans, and the harness will complain about it and die. # Use it like this ... use Test::NeedsDisplay; # ... not like this ... use Test::NeedsDisplay 'anything'; # ... and not like this. use Test::NeedsDisplay (); And that's all there is to do. The module will take care of the rest. TO DO
- Find alternative ways to launch a display on different platforms SUPPORT
Bugs should be reported via the CPAN bug tracker at <http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Test-NeedsDisplay> For other issues, contact the author. AUTHOR
Adam Kennedy <adamk@cpan.org> COPYRIGHT
Copyright 2005 - 2009 Adam Kennedy. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of the license can be found in the LICENSE file included with this module. perl v5.10.0 2009-01-04 Test::NeedsDisplay(3pm)
Man Page