Tchize wrote: >Functional tests will never be complete (you can't cover all game >situation, but you can cover all methods), that does not mean we >shouldn't write them as they are about as easy to write as unit one, and >use the same framework. I even think we should start by writing a few >functionnal unit tests based on current sourceforge bugtrack, while in >parallel begin to write unit tests to cover each crossfire function. > Yes, and also functional tests for some things that haven't caused bugs in the past, but are sorts of things that often do would also be good to make functional unit tests for (such as, spells and ranged weapons fired infront of map edges). Also, even for the non-functional unit tests, the functions will often need a set of data to operate within, and this would in many cases, mean a map.
Alex Schultz _______________________________________________ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire