Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 5 Jul 2002 15:46:13 -0700 (PDT)
From: "B. W. Fitzpatrick" <fitz@apple.com>
To: Ryan Bloom <rbb@ntrnet.net>
cc: dev@apr.apache.org
Subject: Re: [RANT] our test suite sucks
In-Reply-To: <Pine.LNX.4.21.0207051817510.10842-100000@shell.ntrnet.net>
Message-ID: <Pine.GSO.4.44.0207051544560.161-100000@gala.apple.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"


On Fri, 5 Jul 2002, Ryan Bloom wrote:

>
> The original intent for the test suite was that somebody could run the APR
> test suite on their implementation of APR, and be sure that they are 100%
> compatible.  The current test suite doesn't even come close to
> implementing that.  In fact, most of the tests don't even give useful
> information about whether a feature is working as it is supposed to.  I am
> trying to test my new poll implementation, but I am spending more time
> interpreting the test rsults than actually fixing the code.
>
> In the next few weeks, I will be creating a real test suite for APR.  It
> will be either Perl or Python based, and all tests will be required to
> report success or failure only in the default mode.  If more information
> is required, that will be done through a verbose mode, much like the perl
> test suite for httpd.

You might want to consider check, a unit test framework for C. It was
super simple to setup, and adding tests is really a snap:

	http://check.sourceforge.net/

-Fitz, hoping he's not starting a test suite flame war