Re: [cgiapp] Request for comments: Test::WWW::Mechanize::CGIApp

[Barry Moore <suppressed>]

Very nice George.  I have immediate use for this on an app I just  
finished, and perhaps retrofit it onto some existing apps that are  
currently under-tested.  I am getting some errors on make test (OSX  
perl 5.8.6).  It's late so I'm not going to dig into these tonight,  
but this is a welcome addition.

Barry

----------------

Mac:Test-WWW-Mechanize-CGIApp-0.03 root# make test
PERL_DL_NONLAZY=1 /usr/local/bin/perl "-MExtUtils::Command::MM" "-e"  
"test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
t/autorunmode.....ok
t/cgiapp..........ok
t/dispatch........Unable to use the value of instance. at lib/Test/ 
WWW/Mechanize/CGIApp.pm line 131.
# Looks like your test died before it could output anything.
t/dispatch........dubious
        Test returned status 255 (wstat 65280, 0xff00)
DIED. FAILED tests 1-13
        Failed 13/13 tests, 0.00% okay
t/instance........Can't locate object method "dispatch" via package  
"MyDispatch" at t/instance.t line 17.
# Looks like your test died before it could output anything.
t/instance........dubious
        Test returned status 255 (wstat 65280, 0xff00)
DIED. FAILED tests 1-26
        Failed 26/26 tests, 0.00% okay
t/pod.............ok
t/pod_coverage....ok
Failed Test  Stat Wstat Total Fail  Failed  List of Failed
------------------------------------------------------------------------ 
-------
t/dispatch.t  255 65280    13   26 200.00%  1-13
t/instance.t  255 65280    26   52 200.00%  1-26
Failed 2/6 test scripts, 66.67% okay. 39/67 subtests failed, 41.79%  
okay.
make: *** [test_dynamic] Error 2

On Mar 12, 2007, at 3:30 PM, George Hartzell wrote:

> I was looking for a make-myself-useful-and-learn-something project on
> the cgiapp wiki and came across a call for a Mechanize'd tester for
> cgiapp.
>
> I put this together after looking at how the catalyst equivalent
> works.  I'd appreciate any feedback folks care to throw at it.
>
> It has the following issues that I'd like to straighten out:
>
>   o it has a poorly named method, "instance", which can contain either
>     the name of a class (CGI::Application or
>     CGI::Application::Dispatch derived) or a CODE ref that the
>     mechanic uses to handle the request.
>
>     I thought about "handler", but that's pretty thoroughly overloaded
>     in our world.  "request_handler"???
>
>     Anyway, I'd appreciate suggestions.
>
>   o If you use CAP::AutoRunmode, you need to let the mechanic know so
>     that it can also 'use' it, otherwise things Just Don't Work.  The
>     way things are right now it's probably a dependency.  I'll at
>     least need to eval the use statement, but I might be able to do
>     something better.  Require/import on demand doesn't work, I think
>     because AutoRunmode does its magic at compile time.
>
>   o The code'll get a little more cleanup, and the docs will get
>     fluffed up a bit.
>
> It'll do the right thing with packages that inherit from
> CGI::Application (new up an instance and call ->run()) and
> CGI::Application::Dispatch (call the class method ->dispatch()).  You
> can also give it your own sub to call if you'd like to do something
> different.
>
> Without further ado:
>
>   http://shrimp.alerce.com/cgiapp/Test-WWW-Mechanize- 
> CGIApp-0.03.tar.gz
>
> What do you think?
>
> Thanks,
>
> g.
>
>
> ---------------------------------------------------------------------
> Web Archive:  http://www.mail-archive.com/suppressed/
>               http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
> To unsubscribe, e-mail: suppressed
> For additional commands, e-mail: suppressed


---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
             http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed