That sounds to me like testing/verifying a web application. If that is the case, WWW::Mechanize together with Test::HTML::Content might be a solution, as might the HTTP::Webtest kit.
The scripts you'd use for either of the two are different from what you envision - HTTP::Webtest gets close to your usage though.
As I am the author of Test::HTML::Content and WWW::Mechanize::Shell, I would create some extension to WWW::Mechanize::Shell to accept some more commands to test the web pages, and then generate the Perl scripts from those command scripts, which then again, Test::Harness would run for me...
The www-mechanize-dev mailing list on http://www.sourceforge.net has Mark Stosberg on it, who does such stuff.
perl -MHTTP::Daemon -MHTTP::Response -MLWP::Simple -e ' ; # The $d = new HTTP::Daemon and fork and getprint $d->url and exit;#spider ($c = $d->accept())->get_request(); $c->send_response( new #in the HTTP::Response(200,$_,$_,qq(Just another Perl hacker\n))); ' # web
In reply to Re: Keyword parser function mapping module
by Corion
in thread Keyword parser function mapping module
by apprentice
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |