apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Bloom" <...@covalent.net>
Subject RE: [RANT] our test suite sucks
Date Wed, 03 Jul 2002 23:55:37 GMT
GREAT TIP!  I will definitely look at this before I start working on the
suite.

Thanks,

Ryan

----------------------------------------------
Ryan Bloom                  rbb@covalent.net
645 Howard St.              rbb@apache.org
San Francisco, CA 

> -----Original Message-----
> From: B. W. Fitzpatrick [mailto:fitz@apple.com]
> Sent: Friday, July 05, 2002 3:46 PM
> To: Ryan Bloom
> Cc: dev@apr.apache.org
> Subject: Re: [RANT] our test suite sucks
> 
> 
> 
> 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



Mime
View raw message