On 10/27/05, chromatic <[EMAIL PROTECTED]> wrote: > On Thu, 2005-10-27 at 10:26 -0700, jerry gay wrote: > > > we're missing some parts of a testing framework. we don't have the > > ability to write test files in PIR, so we're dependent on a perl > > install for testing. perl's a great language for writing tests anyway, > > and right now we're dependent on perl for parrot's configure and build > > as well. that said, breaking this dependency will make parrot just a > > bit closer to standing on its own. > > We have a Test::Builder port in PIR. I will move up my plan to port > Parrot::Test to use it. > i'm sorry, chromatic, somehow i missed Test::Builder, which looks solid. that's great news about porting Parrot::Test.
> Making a list of the features of Parrot::Test you need in PIR would help > me. > most important to me now are: skip, plan, and the pir_output_* subs. next is pasm_* and language_*. the rest can follow over time, unless somebody else has any input. ~jerry
