[sanexx-commit] SF.net SVN: sanexx: [4]

[<pad...@us...>]

Revision: 4
Author:   paddy_hack
Date:     2006-02-25 06:54:49 -0800 (Sat, 25 Feb 2006)
ViewCVS:  http://svn.sourceforge.net/sanexx/?rev=4&view=rev

Log Message:
-----------
 r9@qed:  olaf | 2006-02-25 23:46:55 +0900
 Document the fact that this project strives to follow a test-driven 
 approach and where it keeps its "use-case" tests.

Modified Paths:
--------------
    trunk/README

Property Changed:
----------------
    /

Property changes on: 
___________________________________________________________________
Name: svk:merge
   - 52428bda-890d-0410-88ad-be188b7e1831:/local:8
   + 52428bda-890d-0410-88ad-be188b7e1831:/local:9

Modified: trunk/README
===================================================================
--- trunk/README	2006-02-25 14:54:36 UTC (rev 3)
+++ trunk/README	2006-02-25 14:54:49 UTC (rev 4)
@@ -25,4 +25,20 @@
   Refer to the 'INSTALL' file for generic installation instructions.
 
 
+DEVELOPMENT STYLE
+
+  sane++ aims to stick to a test-driven development style.  As long as
+  all the tests pass, the sources should be in a releasable state.  Of
+  course, this means that you need to write a test first and only then
+  start coding to make that test pass.
+
+  The most important tests are the "use-case" tests.  Such tests check
+  "end-user functionality", like usability of a sane++ frontend with a
+  regular SANE backend, some real life scenarios in which a user tries
+  to set an option that is not supported by the device.  Such use-case
+  tests are collected in the 'tests/' directory and are run as part of
+  the 'check' target.  That is, running `make check` will execute each
+  and every use-case test.
+
+
  -- Olaf Meeuwissen <pad...@us...>



This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.