Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

source code 7 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • you should think about integrating Apache-Test now before mod_parrot gets too big. ping me if you need help.

    • Won't he need Parrot's Test::Builder first? I mean, it'll be there eventually, but I need one new opcode first....

      • not necessarily.

        conceptually there are two parts to Apache-Test, the client-side *.t tests that act as the browser, and (if you're running mod_perl) the server-side *.pm tests.

        at this point in mod_parrot, I would guess that development is being done by writing some glue code then writing some kind of parrot handler that calls ap_rputs and testing that code with a browser. most of that process can be turned over to Apache-Test, both easing development and forming the start of a test framework. when it comes time to write glue for setting the header_out table or retrieving various request_rec slot values, that can be handled via some additional client-side tests.

        for the server side, I'd imagine that quite a bit of glue would be required. your proposed Test::Builder glue for parrot for one, an Apache::TestRunParrot extension for mod_parrot autoconfiguration magic, not to mention an official Test::Simple 0.49 release so Apache-Test can support Test::More functions on the server side :)

        but all in good time. for the moment, I would expect Apache-Test to be a huge help in mod_parrot development. in fact, if I can get parrot running on my system I'll probably code in the Apache-Test hooks myself and explain it to jeff over a beer :)
        • I like beer. :)
        • I did some reading on Apache::Test and got off to a good start:

          [jeff@groovy mod_parrot]$ make test
          /usr/local/perl/5.8.5-shared/bin/perl t/TEST t/*.t
          [warning] setting ulimit to allow core files
          ulimit -c unlimited; /usr/local/perl/5.8.5-shared/bin/perl /one/home/jeff/build/mod_parrot/t/TEST 't/01RequestRec.t'
          /usr/local/apache2/bin/httpd -d /one/home/jeff/build/mod_parrot/t -f /one/home/jeff/build/mod_parrot/t/conf/httpd.conf -D APACHE2
          using Apache/2.0.50 (prefork MPM)

          waiting 60 seconds for server to start:

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.