From: Charles Comstock <cc1@...>
Date: 2004-08-12T00:41:13+09:00
Subject: Re: Test::Unit output

Nathaniel Talbott wrote:

> On Aug 11, 2004, at 03:36, Charles Comstock wrote:
> 
>> I was curious if there are other test modes on test::unit which are 
>> more descriptive of the progress through each file of testing.  I 
>> think this would be particularly useful for running test cases like 
>> those in the ruby interpreter.  If the interpreter segfaults in the 
>> middle of running tests, and all you have are a bunch of .'s and E's 
>> how are you supposed to tell what it failed on?  Also while the .'s 
>> are alright for a short set, it would seem as if some sort of progress 
>> description over each test file would be more descriptive of the 
>> progress while testing.
>>
>> Has this been gone over before?  Any particular reason for the choice 
>> of the dotted output?
> 
> 
> Did you try passing your test --help on the commandline? I think 
> --verbose is what you're looking for:
> 
>   ntalbott@jacob:~/tmp$ cat t.rb
>   require 'test/unit'
> 
>   class T < Test::Unit::TestCase
>     def test1
>     end
> 
>     def test2
>     end
>   end
> 
>   ntalbott@jacob:~/tmp$ ruby t.rb
>   Loaded suite t
>   Started
>   ..
>   Finished in 0.005947 seconds.
> 
>   2 tests, 0 assertions, 0 failures, 0 errors
>   ntalbott@jacob:~/tmp$ ruby t.rb --verbose
>   Loaded suite t
>   Started
>   test1(T): .
>   test2(T): .
> 
>   Finished in 0.009733 seconds.
> 
>   2 tests, 0 assertions, 0 failures, 0 errors
> 
> HTH,
> 
> 
> Nathaniel
> Terralien, Inc.
> 
> <:((><
> 
> 
> 

Right that's per test listing, I was more looking for per file listing 
or something like that.  Hate to mention the p language, but I had to 
install something from cpan last night to run someone elses code and I 
was reminded of how nice there test ouput was.  They seemed to follow 
the general format of:
t/testfilename test#/ofTotal (cycling through number complete and then 
outputing ok when done)

If it's just one file I don't really think you need to necessarily know 
test by test, above would be useful to find it in a specific file 
though.  Anyway I was impressed by there format I guess.  Particularly 
haven been bitten for a while with a segfault running the test suite 
bundled with the interpreter in ruby.  I found out later what was 
killing with it, but after a hundred of those dots go by it's kinda hard 
to keep track of what test you might be on.

Hmm maybe i'll write my own test-suite formatter or something.

Charlie