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

use Perl Log In

Log In

[ Create a new account ]

pudge (1)

pudge
  (email not shown publicly)
http://pudge.net/
AOL IM: Crimethnk (Add Buddy, Send Message)

I run this joint, see?

Journal of pudge (1)

Sunday July 08, 2001
07:37 AM

test harness

[ #389 ]
I got the test harness working on MacPerl, except that it still doesn't quite work. The problem is that normally when you run a perl script, you run it under MPW. Then if that script calls out to system() or qx//, it runs under ToolServer. This causes a few small problems for us anyway in testing, because %ENV does not carry over to ToolServer (in my experience, anyway :-).

So anyway, when you run under the test harness, now you run the harness script under MPW, and when it calls each individual script, that runs under ToolServer. And if that test script calls out to system() or qx// ... it cannot call out to ToolServer since ToolServer is already being used. So it fails. D'oh!

Anyway, so I wrote an MPW script to run all the tests. Then I realized that some tests don't print "not ok" if a test fails, but instead just print nothing. And sometimes, "ok" is printed more than once for a test. So, I wrote a perl script to parse the results from the MPW script. :-)

Anyway, the result is below. I found one test that was falsely reported as succeeding (lib/dprof.t).

:lib:db-btree.t
:lib:db-hash.t
:lib:db-recno.t
:lib:dosglob.t
:lib:dprof.t
:lib:ftmp-mktemp.t
:lib:ftmp-posix.t
:lib:ftmp-security.t
:lib:ftmp-tempfile.t
:lib:ndbm.t
:lib:posix.t
:op:die_exit.t
:op:magic.t
:op:misc.t
:op:sprintf.t
:pragma:warnings.t