Difference between revisions of "Quality assurance"

From GNUstepWiki
Jump to navigation Jump to search
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
 
== Introduction ==
 
== 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.
+
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 way to guarantee this as it's always possible to make errors in comitting.  However, there are 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.
 
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.
+
It is also good to check out and build code immediately after you have comitted it ... as a sanity check to ensure that you comitted the correct version.
 +
 
 +
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 of 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
 
See http://wiki.gnustep.org/index.php/Developer_FAQ#How_can_I_take_part_with_a_GNUstep_autobuilder_for_the_testfarm.3F
  
[[User:Aperez|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. ''
+
We paeticularly need someone with a windows machine to volunteer to take part in this scheme.
 
 
== Compilability test ==
 
 
 
As it is frustrating to check out CVS and have it fail to build for such a trivial reason.
 
 
 
Some sort of automated QA mechanism is necessary, where, upon a new CVS check-in to -base, for example, it is be checked out by an automated QA system and compiled on Linux/x86 as a  baseline test. The results of the compilation would be placed on a
 
webpage. If compilation breakage to any part of -core happened, a
 
message would be sent to -dev notifying the core team that this had
 
happpened, the offending file, and the version of the file in CVS at
 
which the breakage occurred.
 
 
 
Idea of a primitive test script for compilability:
 
 
 
cd test_directory
 
rm -rf core GNUstep-test-root
 
cvs co core
 
cd core
 
./build-all $test_directory/GNUstep-test-root &> test-log.txt
 
 
 
[[Category:Project procedures]]
 

Latest revision as of 07:59, 29 October 2006

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 way to guarantee this as it's always possible to make errors in comitting. However, there are 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.

It is also good to check out and build code immediately after you have comitted it ... as a sanity check to ensure that you comitted the correct version.

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 of 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

We paeticularly need someone with a windows machine to volunteer to take part in this scheme.