[commit-womb] qualitycode qualitycode.texi

[Ludovic Courtès]

CVSROOT:        /sources/womb
Module name:    qualitycode
Changes by:     Ludovic Courtès <civodul>       10/11/23 08:48:30

Modified files:
        .              : qualitycode.texi 

Log message:
        Add a stub about testing.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qualitycode/qualitycode.texi?cvsroot=womb&r1=1.5&r2=1.6

Patches:
Index: qualitycode.texi
===================================================================
RCS file: /sources/womb/qualitycode/qualitycode.texi,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- qualitycode.texi    23 Nov 2010 08:27:36 -0000      1.5
+++ qualitycode.texi    23 Nov 2010 08:48:29 -0000      1.6
@@ -1,5 +1,5 @@
 \input texinfo   @c -*-texinfo-*-
address@hidden $Id: qualitycode.texi,v 1.5 2010/11/23 08:27:36 civodul Exp $
address@hidden $Id: qualitycode.texi,v 1.6 2010/11/23 08:48:29 civodul Exp $
 @comment %**start of header
 @setfilename qualitycode.info
 @set UPDATED 18 November 2010
@@ -48,6 +48,7 @@
 
 @menu
 * Memory management::
+* Testing::                     
 * GNU Free Documentation License::
 * Index::
 @end menu
@@ -175,6 +176,48 @@
 @c http://www.hpl.hp.com/personal/Hans_Boehm/gc/leak.html
 
 
address@hidden Testing
address@hidden Testing
+
address@hidden
+Program testing can be used to show the presence of bugs, but never to
+show their absence!
+
+--- Edsger W. Dijkstra.
address@hidden quotation
+
address@hidden
+* Test coverage::               What's left to test?
+* Writing new tests::           When to write tests?
+* Practical details::           Support for test suites.
address@hidden menu
+
address@hidden Test coverage
address@hidden Test coverage
+
+TODO: Write about feedback from test coverage report tools such as
address@hidden Options, GCC's @code{--coverage},, gcc, GCC Reference
+Manual} and @url{http://ltp.sourceforge.net@/coverage@/lcov.php, LCOV};
+same for @ref{Code Coverage, Guile,, guile, GNU Guile Reference Manual}.
+
address@hidden Writing new tests
address@hidden Writing new tests
+
+TODO: Write something about test-driven development, and the addition of
+a test for each bug fix.
+
address@hidden Practical details
address@hidden Practical details
+
+TODO: Write something about @ref{Tests, Automake support for test
+suites,, automake, The GNU Automake Reference Manual}, @ref{Using
+Autotest, Autotest,, autoconf, The GNU Autoconf Reference Manual}, and
+possibly DejaGNU and language-specific frameworks for C/C++/Guile/Emacs.
+
+
address@hidden TODO: Add something about Frama-C or other static analysis tools?
+
+
 @node GNU Free Documentation License
 @appendix GNU Free Documentation License