Re: Testing Abstract Classes

Re: Testing Abstract Classes

[Artur Biesiadowski]

[-- Attachment #1: Type: text/plain, Size: 0 bytes --]



[-- Attachment #2: Re: Testing Abstract Classes --]
[-- Type: message/rfc822, Size: 1292 bytes --]

From: Artur Biesiadowski <abies00@wp.pl>
To: Mauve Discuss <mauve-discuss@sources.redhat.com>
Subject: Re: Testing Abstract Classes
Date: Mon, 23 Dec 2002 20:40:54 +0100
Message-ID: <3E0766C6.50603@wp.pl>

<div class="moz-text-flowed" style="font-family: -moz-fixed">Daryl Lee wrote:
> I ran JDK 1.1 tests of FileReader before noticing it was an abstract class.
> Since an abstract class can't be instantiated, is the notion of testing it
> meaningful?  If so, what would be a good general approach?  Pending an
> answer, I'm going to skip over this and all other abstracts.  

We are talking about testing implementation behavior, not interfaces.

Just create a test which subclasses FileReader and calls all 
non-abstract methods in parent class to check if their results are ok. 
You might need to implement some of abstract methods in meaningful way, 
but this can actually make testing easier.

Artur

</div>

Re: Testing Abstract Classes

[Dalibor Topic]

--- Daryl Lee <dlee@altaregos.com> wrote:
> I ran JDK 1.1 tests of FileReader before noticing it
> was an abstract class.
> Since an abstract class can't be instantiated, is
> the notion of testing it
> meaningful?  If so, what would be a good general
> approach?  Pending an
> answer, I'm going to skip over this and all other
> abstracts.  

You can create a wrapper class with stubbed abstract
methods, and use that to test the conditions on the
non-abstract methods hold. I've written some tests for
java.io.Reader in kaffe's regression test suite that
way.

best regards,

dalibor topic

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

Testing Abstract Classes

[Daryl Lee]

I ran JDK 1.1 tests of FileReader before noticing it was an abstract class.
Since an abstract class can't be instantiated, is the notion of testing it
meaningful?  If so, what would be a good general approach?  Pending an
answer, I'm going to skip over this and all other abstracts.  

-- 
Daryl Lee 
Open the present--it's a gift.