From: Dmitri Colebatch <dim@...>
Date: 2003-01-10T04:48:54+09:00
Subject: Re: Test::Unit fails w/no tests [was: testunit 0.1.6 problems]

> > [..] I'm not sure that's a practice that ought to be supported. As an
XP'er,
> > I'd say, "YAGNI!" and delete the TestCase as soon as it's empty, knowing
> > that it's cinchy to add back  [..]
>  >
> > [..] I'd like to hear some more on this first (if there are any other
opinions).
>
> I like the failure when you have an empty TestCase for the XP YAGNI reason
> you stated above.

can I clarify this - the claim is taht a test without any assert checks is a
fail - not an empty test yes?  I assume that there is no way of determining
if the method is in fact empty?  yes?

for instance - does this constitute a failure?

    def test_null_object
        nullObject = NullObject.new
        nullObject.method1
        nullObject.method2
        nullObject.method3
    end

to check that I have a null object that implements those methods and doesn't
raise errors when called.

as I understand the thread, because this has no assert statements, it would
be deemed a failure - correct?

cheers
dim