From: Gennady Date: 2003-06-25T02:21:49+09:00 Subject: Test::Unit 0.1.8 reporting problem This is a multi-part message in MIME format. ------=_NextPart_000_000E_01C33A3A.70EF48F0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable I recently upgraded my testunit package from 0.1.6 to 0.1.8. Besides = renaming set_up to setup and tear_down to teardown (I new that I would = have to do it) I found another problem, or nuisance, rather:=20 When outputting a single '.' to stdout on a test completion (before it = was to stderr, I guess), stdout is not flushed. So you actually see = results only after all tests are done. If a test takes some time to = finish, you do not see any output for a while, and then a burst of dots = are dumped on you. I fixed it on my system in "test/unit/ui/console/testrunner.rb" by = adding @io.flush after @io.write in "output_single" method, however it = would be nice to have it fixed it the RAA distribution of testunit. Regards,=20 Gennady. ------=_NextPart_000_000E_01C33A3A.70EF48F0 Content-Type: text/html; charset="koi8-r" Content-Transfer-Encoding: quoted-printable

I recently upgraded my testunit package = from 0.1.6=20 to 0.1.8. Besides renaming set_up to setup and tear_down to teardown (I = new that=20 I would have to do it) I found another problem, or nuisance, rather:=20

When outputting a = single '.' to stdout on=20 a test completion (before it was to stderr, I guess), stdout is not = flushed. So=20 you actually see results only after all tests are done. If a test takes = some=20 time to finish, you do not see any output for a while, and then a burst = of dots=20 are dumped on you.

I fixed it on my system in=20 "test/unit/ui/console/testrunner.rb" by adding @io.flush after @io.write = in=20 "output_single" method, however it would be nice to have it fixed it the = RAA=20 distribution of testunit.

Regards,

Gennady.

------=_NextPart_000_000E_01C33A3A.70EF48F0--