Quality assurance

Introduction

Sometimes the GNUstep does not work as expected or can not be built at all. If the actual code which gets committed (which IMHO is really a basline requirement) was tested then this should not happen. Unfortunately there is no waay to guarantee this as it's always possible to make errors in comitting. However, there are two things which can help with this.

As a standard procedure developers should build the code and run the testsuites (http://svn.gna.org/viewcvs/gnustep/tests/testsuite/trunk/) before comitting changes.

Clean builds are run on a nightly basis and the results are sent to the gnustep developers mailing list. It is important that people volunteer to have their machines participate in this process so that developers can be made aware os system dependent problems as soon as possible. See http://wiki.gnustep.org/index.php/Developer_FAQ#How_can_I_take_part_with_a_GNUstep_autobuilder_for_the_testfarm.3F

Aperez: I'd also like to set this up for win32, since that seems to be the thing that breaks fairly often as other patches go into -core.