From: John Smith Date: 2009-12-31T13:05:58+09:00 Subject: Re: Test::unit assertion pass scenario Why is a good question. First, the extra info is not for myself, nor would it be for any of the devs who may run it. The theory is that anyone who writes the test or uses them regularly should be familiar with what is being tested anyway, and hence, only the failures really need further investigation. It's more of a CYA item for those who are, shall we say, not in the know. Ryan Davis wrote: > On Dec 30, 2009, at 17:41 , John Smith wrote: > >> Yep, the example below is exactly the way I'm using it. >> However, as demonstrated in your example, the 259 assertions that were >> run (and passed) do not display any kind of passing checkpoint, the way >> it would have if any of those assertions failed. >> >> Basically, I am looking for a way to provide info just for both passed >> and failed assertions, similar to what is done when an assertion fails. > > Your use of "info" is pretty nebulous. > >>>> ....................................................................................................... >>>> Finished in 0.214105 seconds. >>>> >>>> 103 tests, 259 assertions, 0 failures, 0 errors, 0 skips > > All of that is "info". > > What do you want it to do differently, and (more importantly) WHY? -- Posted via http://www.ruby-forum.com/.