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
resolv
Thanks for this, David
Dan
> -Original Message-
> From: David Scott [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 11 April 2007 10:42 a.m.
> To: [EMAIL PROTECTED]
> Subject: Re: [cgiapp] Tests and CGI::Application
>
> Dan,
>
> I think testing is easy under
Dan,
I think testing is easy under C:A apps and I've
automated a few projects.
I think the Test::WWW::Mechanize is a great way to
test.
To illustrate how to test C:A parts, I created a small
application with tests on a small C:A app and its
underlying object. Then I created a way to see the
out
Dan,
I think testing is easy under C:A apps and I've
automated a few projects.
I think the Test::WWW::Mechanize is a great way to
test.
To illustrate how to test C:A parts, I created a small
application with tests on a small C:A app and its
underlying object. Then I created a way to see the
out
Gabor Szabo wrote:
> You to write a bunch of test with the standard Mechanize API and then run
> them either using Test::WWW::Mechanize::CGI *without* a web server
> or using Test::WWW::Mechanize after setting up a the application with
> a real web server.
I agree with Gabor here. If I'm writing
If you look at Yapcom, I have been using
Test::WWW::Mechanize::CGI and
Test::WWW::Mechanize
see the get_mech mehtod in
http://svn1.hostlocal.com/yapcom/yapcom/trunk/t/lib/YAPC/Test.pm
and the use in these test:
http://svn1.hostlocal.com/yapcom/yapcom/trunk/t/web/
You to write a bunch of test wit
sts.erlbaum.net
> Subject: Re: [cgiapp] Tests and CGI::Application
>
> Dan Horne writes:
> > [...] I guess
> > Test::WWW::Mechanize is one module to look at, but I
> should also be looking > at calling my controller code
> directly as well as going through the front
Dan Horne writes:
> [...] I guess
> Test::WWW::Mechanize is one module to look at, but I should also be looking
> at calling my controller code directly as well as going through the front
> end.
> [...]
I don't have a lot of experience to share, but I have wrapped up a
CGIApp specific extensi
