Test::More and Tests in PIR

[Chromatic]

Hi all,

Here's a first shot at Test::More in pure PIR. It only supports plan(),
ok(), and is() (for integers, floats, strings, and PMCs) right now. If
everyone's reasonably happy, I'll check it in. Everything's pretty
straightforward here and any decent PIR hacker should be able to follow
along.

I've also attached a pure PIR test script that uses
Test::Builder::Tester.

One recurring problem I ran into is the one where you can't use
load_bytecode on a library file multiple times, else it warns about
reinitialization. I don't remember if there is a workaround, so I
welcome any suggestions.

The next step is diving into Parrot::Test to see what it needs and what
I already have working.

At some point we ought to figure out where tests for libraries should
go. I have pure PIR tests for Test::Builder, Test::Builder::Tester, and
Test::More now. I've attached the latter.

-- c

[Leopold Toetsch]

On Nov 26, 2005, at 22:16, chromatic wrote:

> Hi all,
>
> Here's a first shot at Test::More in pure PIR. It only supports
> plan(),
> ok(), and is() (for integers, floats, strings, and PMCs) right now. If
> everyone's reasonably happy, I'll check it in.

chromatic please make that sentence: 'If no one's unhappy, ...'

looks good to me ...

thanks,
leo

[Chromatic]

On Mon, 2005-11-28 at 23:00 +0100, Leopold Toetsch wrote:

> chromatic please make that sentence: 'If no one's unhappy, ...'

My goals are more modest than pleasing everyone... but checked in as
#10339.

I'm thinking we need a little harness file to launch the tests in
specific directories without hardcoding languages... t/lib/harness,
t/doc/harness, or something like that.

-- c