It would be cool if ci-reporter could capture any system out/err that occured during the test run. The standard ant/junit
reporter does this already and its proved very useful.
If it helps ant normally stores it under:
<system-out><![CDATA[ blah ....
]]></system-out>
and
<system-err><![CDATA[ blah ....
]]></system-err>
I guess one (hacky) method would be to redefine $stdout and $stderr and collect results, or maybe overide IO.puts.
p. |