This is definitely a good approach, but what it lacks is coverage
reporting capabilities, should you want to know how much of your code is
covered.
Since someone previously posted about T:W:M:CGI, I've been playing
around with that and it also has some flaws that I haven't been able to
resolve - filed a bug report:
http://rt.cpan.org/Public/Bug/Display.html?id=26203
CGIApp testing is really in a state of chaos, in that there is no one
"ring to rule them all", so to speak. I wrote about this a while ago,
but never got around to the implementation:
http://www.mail-archive.com/cgiapp@lists.erlbaum.net/msg04299.html
It looks like George Hartzell has one solution posted (thanks, George!)
-- I need to check that out:
http://www.mail-archive.com/cgiapp@lists.erlbaum.net/msg06081.html
- Jason
David Scott wrote:
Dan,
[snip]
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/cgiapp@lists.erlbaum.net/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
