Ahh, good fun. Can't wait to start looking at making some, some of the functional tests could be fun to make.
Alex Schultz tchize wrote: >The first shoot of unit test has been commited in cvs, along with a >few very nice add-ons to configure script. The framework has been >configured for test/unit/** > >other directories will be linked later, there is already plenty of >file to work on :) >to run unit tests, do a >./configure >make >make -k check > >the -k is important, it tells make to continue even if some tests fails. >I have made empty testcase failing for all existing crossfire files. >We now need lots of apes / monkeys, to write the test code to have >them success. An example finished file is test/common/check_shstr.c > >all test logs go to test/logs as xml files (will be usefull for >automated webpage generation with nightliy test result on sourceforge :p) > >screen ouput of test are driven by environment variable >CK_VERBOSITY > which can have the values "silent", "minimal", "normal, "verbose" > >first doc written in doc/Developers/testplans (this was the previous >test docs, it as been replaced) > >Have fun, code well, let's get all those test filled :) > >Tchize >David Delbecq > _______________________________________________ crossfire mailing list [email protected] http://mailman.metalforge.org/mailman/listinfo/crossfire
