Test suite done.

[rb...@rkbloom.net]

The new test framework is essentially done.  There are some features I
would still like to add.  However, the suite has feature parity with the
CuTest framework that we are currently using.  The suite was written from
scratch, but it has many of the same advantages of the CuTest framework
(ie small, fast, and unobtrusive), but it fixes many of the CuTest issues.

An example of how the suite works can be found at:

https://rkbloom.dyndns.org:444/abts/

Just look at test.c or test1.c for the actual test suite code.  If nobody
complains, I will create a simple script to migrate our existing test
suite to this framework.  If anybody has automated scripts that are using
the output, this change will break those scripts.

Ryan

RE: Test suite done.

[rb...@rkbloom.net]

__FILE__ is already added to the suite, so the output always includes the
actual file name.  As for __LINE__, it is something that I have considered
adding to the log_message function, but I am not convinced of it's
usefulness once we have the ability to print out custom messages.  In
CuTest, it is essentially required, because the framework doesn't really
let you add debug messages.

Ryan

On Sun, 2 May 2004, Nicolas Belan wrote:

> Hi,
>
> I am currently using CuTest for a project.
> When a test fails, I added __LINE__ __FILE__ as argument of functions
> to get the exact place where it failes.
> I know, this is just a detail, but it could be nice that something could be
> added to the new framework .
>
> Nicolas
>
> > -----Message d'origine-----
> > De : rbb@rkbloom.net [mailto:rbb@rkbloom.net]
> > Envoye : samedi 1 mai 2004 20:38
> > A : dev@apr.apache.org
> > Objet : Test suite done.
> >
> >
> >
> > The new test framework is essentially done.  There are some features I
> > would still like to add.  However, the suite has feature parity with the
> > CuTest framework that we are currently using.  The suite was written from
> > scratch, but it has many of the same advantages of the CuTest framework
> > (ie small, fast, and unobtrusive), but it fixes many of the CuTest issues.
> >
> > An example of how the suite works can be found at:
> >
> > https://rkbloom.dyndns.org:444/abts/
> >
> > Just look at test.c or test1.c for the actual test suite code.  If nobody
> > complains, I will create a simple script to migrate our existing test
> > suite to this framework.  If anybody has automated scripts that are using
> > the output, this change will break those scripts.
> >
> > Ryan
> >
> >
> >
>
>

RE: Test suite done.

[Nicolas Belan <nb...@tele2.fr>]

Hi,

I am currently using CuTest for a project.
When a test fails, I added __LINE__ __FILE__ as argument of functions
to get the exact place where it failes.
I know, this is just a detail, but it could be nice that something could be
added to the new framework .

Nicolas

> -----Message d'origine-----
> De : rbb@rkbloom.net [mailto:rbb@rkbloom.net]
> Envoye : samedi 1 mai 2004 20:38
> A : dev@apr.apache.org
> Objet : Test suite done.
>
>
>
> The new test framework is essentially done.  There are some features I
> would still like to add.  However, the suite has feature parity with the
> CuTest framework that we are currently using.  The suite was written from
> scratch, but it has many of the same advantages of the CuTest framework
> (ie small, fast, and unobtrusive), but it fixes many of the CuTest issues.
>
> An example of how the suite works can be found at:
>
> https://rkbloom.dyndns.org:444/abts/
>
> Just look at test.c or test1.c for the actual test suite code.  If nobody
> complains, I will create a simple script to migrate our existing test
> suite to this framework.  If anybody has automated scripts that are using
> the output, this change will break those scripts.
>
> Ryan
>
>
>