Project Fairdice
[Home] [Docs] [Users] [Gaming] [Crypto] [Devel] [Download] [Help]

Developers : Build and Test

Currently unit testing consists of manually running frdi_test.exe and hand checking the output. The systematic testing consists of manually running the scenarios and hand checking the output.

The way it ought to work is having a nightly automated build and test cycle on each platform, leading to a nice traffic lights indicator of whether the build is broken and who broke it. (See for example how Mozilla does it.)

The make file has no configure script. It needs to be written to use autoconf (and probably automake). It should also have the include file dependancy tree altered to show the true dependancies.

Nightly snapshots would be nice.

CVS guidelines. We should have some. Suggestions?


(TOP)(UP)