With recent updates (just in the past week), partcl can now actually use the tcltest library that comes with tcl 8.5.4 [1]
For some time, we have been limping along with partcl's hand-rolled Test::More analog on a slightly processed version of tcl's *.test files. The current version of "make spectest" is actually processing the _raw_ .test files from the cvs repository.[2] While tcltest doesn't generate TAP, being able to run the spec test using the native testing tool is a big step forward. I'm doing a test run now, and will followup tomorrow, when it finishes. Despite the caveats below, I'm pretty happy with this progress[3]: $ tclsh8.5 t_tcl/llength.test llength.test: Total 6 Passed 6 Skipped 0 Failed 0 $ ./tclsh t_tcl/llength.test 0: Total 6 Passed 6 Skipped 0 Failed 0 expected boolean value but got "" [4] Regards. -- Will "Coke" Coleda [1] Not exactly a pristine copy: one of the core features of tcltest (where should I send my output) requires some relatively advanced functionality - tcl's tests are not designed like perl6's to allow new implementations to ease into things. I've tacked on a replacement sub in our copy of tcltest that for now always says "just print to stdout". Still, that's a oneline proc body compared to the original 3375 lines of tcltest.tcl [2] Not all of them work. Also, we're not just running "all.tcl" which would run all the tests; we're running them individually. [3] No, not that six whole tests pass. :P [4] Yes, there's an error, and the filename has magically integerfied. Shhh. Don't ruin my moment. _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
