[crossfire] Unit tests, request for comments

[tchize]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Those won't be macros but function,  they do too complicated stuff to
be macros. Those will be part of the unit test toolkit (directory
crossfire/test/toolkit), which will made available to each test_xxx.
Various helpers will be developped and made available to users as unit
test development advance.


Alex Schultz a écrit :

> Another thing, I'm thinking that in order to make such tests very
> easy to make, a variety of convenience macros would be good to put
> here. Such as perhaps one to run the main server cycle for x ticks,
> and perhaps one to run the main server cycle until another
> specified macro or function returns non-zero. It might also be good
> to make some little macros such as one for map loading, that has a
> slightly simpler interface than the normal one (don't need that
> last parameter for most functional tests). Having a good variety of
> such convenience functions and macros would make building
> functional tests easy to learn by example even for someone who does
> not know much C at all, and would make it faster for those who do.
>
>
> tchize wrote:
>
>> Includes ======== Testcases will share some include files not
>> present in crossfire core. Those test specific headers will be
>> put in test/includes
>>
>
> _______________________________________________ crossfire mailing
> list crossfire at metalforge.org
> http://mailman.metalforge.org/mailman/listinfo/crossfire
>
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEE/LaHHGOa1Q2wXwRAkrxAJ0fJOLQZzftcr3z4/hiV5x8uSWGvACgxOas
uuajkXK4Kt5rZzJptC5wxQc=
=gRkG
-----END PGP SIGNATURE-----