This is the mail archive of the
mailing list for the Mauve project.
Re: Testing Abstract Classes
- From: Dalibor Topic <robilad at yahoo dot com>
- To: Daryl Lee <dlee at altaregos dot com>, Mauve Discuss <mauve-discuss at sources dot redhat dot com>
- Date: Tue, 24 Dec 2002 09:56:46 -0800 (PST)
- Subject: Re: Testing Abstract Classes
--- Daryl Lee <firstname.lastname@example.org> 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
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
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.