From: "Zachary P. Landau" <kapheine@...>
Date: 2004-08-15T02:27:47+09:00
Subject: Re: Test::Unit output

--Wtrm9ATX0sn6fFKv
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Aug 11, 2004 at 04:36:18PM +0900, Charles Comstock wrote:
> I was curious if there are other test modes on test::unit which are more=
=20
> descriptive of the progress through each file of testing.  I think this=
=20
> would be particularly useful for running test cases like those in the=20
> ruby interpreter.  If the interpreter segfaults in the middle of running=
=20
> tests, and all you have are a bunch of .'s and E's how are you supposed=
=20
> to tell what it failed on?  Also while the .'s are alright for a short=20
> set, it would seem as if some sort of progress description over each=20
> test file would be more descriptive of the progress while testing.
>=20
> Has this been gone over before?  Any particular reason for the choice of=
=20
> the dotted output?

I just came across these CUnit screenshots today[1].  They seem to do a
pretty good job of keeping the output nice and clear.  I don't have any
major issues with the current Test::Unit output, but I figured I'd show
these.

[1] http://gethos.net/opensource/cunit_screenshots.php

--
Zachary P. Landau <kapheine@hypa.net>
GPG: gpg --recv-key 0x24E5AD99 | http://kapheine.hypa.net/kapheine.asc

--Wtrm9ATX0sn6fFKv
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBHkv1CwWyMCTlrZkRAu/3AJ0b4NoM7Gel7xgHz/fRwRYsyICr0wCfbheJ
dj9TYnR+/5wdxT1Dul8AVlM=
=liQg
-----END PGP SIGNATURE-----

--Wtrm9ATX0sn6fFKv--