[GRASS-SVN] r61572 - grass/trunk/lib/python/docs/src

svn_grass at osgeo.org svn_grass at osgeo.org
Fri Aug 8 19:15:22 PDT 2014


Author: wenzeslaus
Date: 2014-08-08 19:15:21 -0700 (Fri, 08 Aug 2014)
New Revision: 61572

Modified:
   grass/trunk/lib/python/docs/src/gunittest_testing.rst
Log:
gunittest: testing C functions using special module

Modified: grass/trunk/lib/python/docs/src/gunittest_testing.rst
===================================================================
--- grass/trunk/lib/python/docs/src/gunittest_testing.rst	2014-08-08 21:33:05 UTC (rev 61571)
+++ grass/trunk/lib/python/docs/src/gunittest_testing.rst	2014-08-09 02:15:21 UTC (rev 61572)
@@ -422,10 +422,21 @@
 in Python. See section :ref:`test-python` for reference.
 
 However, more advantageous and more preferable (although sometimes
-more complicated) solution is to write a special program, possibly
-GRASS module (i.e., using ``G_parser``).
+more complicated) solution is to write a special program, preferably
+GRASS module (i.e., using ``G_parser``). The dedicated program can
+provide more direct interface to C and C++ functions used by
+a GRASS module then the module and can also serve for doing benchmarks
+which are not part of the testing.
+This can approach can be applied to both 
 
+See the example in ``lib/raster3d`` GRASS source code directory
+to create a proper Makefiles. A ``main()`` function should be written
+in the same way as for a standard module.
 
+Having a GRASS module for the purpose of testing you can write test
+as if it would be standard GRASS module.
+
+
 .. _test-python:
 
 Tests of Python code



More information about the grass-commit mailing list