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
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...)
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.
Apache-Test (Score:2)
Re:Apache-Test (Score:1)
I'll be sure to ping you, as the only experience I have with it is from your talks.
Re:Apache-Test (Score:1)
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 (Score:2)
conceptually there are two parts to Apache-Test, the client-side
*.ttests that act as the browser, and (if you're running mod_perl) the server-side*.pmtests.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_rputsand 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. whenRe:Apache-Test (Score:1)
Re:Apache-Test (Score:1)
Re:Apache-Test (Score:2)
guess you didn't want to wait around for me to do it. shucks - I was looking forward to installing parrot...
Re:Apache-Test (Score:1)
Re:Apache-Test (Score:1)
Re:Apache-Test (Score:1)
register_multior whatever you and Leo decided. It's very handy to have Parrot dispatch on the arguments passed tois()instead of having to do it myself.Re:Apache-Test (Score:1)