chromatic wrote:
Instead of printing "done" at the end of code, the *_output_*() test functions
now check that Parrot's exit code is zero. This prevents the test suite from
eating segfaults, as it used to.
If you want to test that Parrot exits with an error given buggy code, use the
*_error_output_* functions.
-- c
Would you be able to write that up as a patch to docs/tests.pod?
Since I haven't been involved with writing tests in Parrot, I'm not sure
exactly what you're getting at -- so any attempt on my part to write the
patch would probably go astray.
Thank you very much.
