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.
 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