From: Florian Gross <flgr@...>
Date: 2004-05-30T23:58:40+09:00
Subject: Re: Test::Unit: assert_follows_spec() (or something like that)

gabriele renzi wrote:

>>>just a question: what if you need many tests per method/class?
>>Many tests or many assertions?
> Mh.. I'd say tests.
> I believe that, once you find a bug in , say, a method, you should add
> a test for it after you fix it. Probably the test is just one
> assertion, anyway. What happens to the doctests ? do you let them grow
> endlessy?

No, I think you should only put tests in there that also have a strong 
purpose as examples. I think it's actually okay to have those tests that 
are cloaked as example code in the documentation and stuff that does 
deeper testing in regular test suits.

But it might also make sense to put all of them into the documentation 
so that the user knows for sure what belongs to the interface of the 
method (the things that are tested for) and what's implementation. 
(Unspecified behavior, the things that aren't tested for.)