All the Perl that's Practical to Extract and Report

source code

jhorwitz on 2004-09-20T19:31:56

Get your mod_parrot here.

Apache-Test

geoff on 2004-09-20T19:41:36

you should think about integrating Apache-Test now before mod_parrot gets too big. ping me if you need help.

Re:Apache-Test

jhorwitz on 2004-09-20T19:49:43

Integrating Apache-Test BEFORE mod_parrot gets too big? BRILLIANT!

I'll be sure to ping you, as the only experience I have with it is from your talks.

Re:Apache-Test

chromatic on 2004-09-20T20:39:28

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

Re:Apache-Test

geoff on 2004-09-20T22:38:01

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 :)

Re:Apache-Test

jhorwitz on 2004-09-20T23:38:32

I like beer. :)

Re:Apache-Test

jhorwitz on 2004-09-23T18:44:28

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: .
waiting 60 seconds for server to start: ok (waited 0 secs)
server localhost.localdomain:8529 started
t/01RequestRec....ok
All tests successful.
Files=1, Tests=1,  2 wallclock secs ( 1.16 cusr +  0.19 csys =  1.35 CPU)
[warning] server localhost.localdomain:8529 shutdown

Re:Apache-Test

geoff on 2004-09-23T20:13:07

sweet!



guess you didn't want to wait around for me to do it. shucks - I was looking forward to installing parrot...

Re:Apache-Test

jhorwitz on 2004-09-23T20:16:25

Hey, I'm gonna need all the help I can get!

Re:Apache-Test

Elian on 2004-09-20T23:37:19

Which opcode? (And if you really need it you can always buy one off of Damian -- As I remember he has two he bought at auction a YAPC::EU or two back...)

Re:Apache-Test

chromatic on 2004-09-21T15:15:13

register_multi or whatever you and Leo decided. It's very handy to have Parrot dispatch on the arguments passed to is() instead of having to do it myself.

Re:Apache-Test

Elian on 2004-09-21T15:22:26

Ah, the MMD for subs. 'Kay, I'll work that one in.