Do not pipe "oneTimeTearDown"

[Google Code Exporter]

oneTimeSetUp is not piped to the output file although onTimeTearDown is.

It is not consistent. 

Given that piping onTimeTearDown creates a subshell and prevent users of 
modifying variables of shunit2 (e.g. suite name) I would propose not to pipe it 
either.

Original issue reported on code.google.com by [e-mail] on 30 Apr 2013 at 9:20

[Google Code Exporter]

Could you provide some sample code that demonstrates the behavior you see? 
Neither functions are piped in shUnit2, and both should behave exactly the same.

Original comment by [e-mail] on 20 May 2013 at 6:16

[Google Code Exporter]

Hello, 

I apologize for the confusion. I had used the patch proposed in issue 16. The 
pipe I was referring to is not present in the official version of shunit2, only 
in the patch. Thus we agree.

You can close this issue. 

Thank you 

Original comment by [e-mail] on 21 May 2013 at 12:12