comment on

That is pretty darned close to what I asked for! Thanks!

WWW::Mechanize is the exact mid-level glue I need to develop complete code coverage. What it lacks as a test platform is a consistent way to represent the inputs in external files, and a consistent way to evaluate the return values of a form POST. I'm leaning toward developing these features to work with the module.

Hmm, WWW::Mechanize::FormFiller looks like it handles the input side rather well.

I know I'm not going to escape all the drudgery in developing my tests. But I have an extreme case of Laziness, and I'd like to duck as much of the drudge as I can. Also I'd like to build on others' work in case I come up with something useful enough to share. That way I don't have to maintain the whole pile myself. (More Laziness. At least I'm consistent. 8)

"Even if you are on the right track, you'll get run over if you just sit there." - Will Rogers

In reply to Re: CGI Test Framework? by hbo
in thread CGI Test Framework? by hbo

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Just another Perl shrine
	PerlMonks