Changes between Version 19 and Version 20 of GSoC/2014/TestingFrameworkForGRASS

Timestamp:

May 26, 2014, 10:43:27 AM (10 years ago)

Author:

wenzeslaus

Comment:

problem of environment specific outputs, idea to use doctest's OutputChecker

GSoC/2014/TestingFrameworkForGRASS

@@ -234 +234 @@
 
 
-== Data types to be checked ==
+== Comparing results ==
 
 We must deal especially with GRASS specific files such as raster maps. We consider that comparison of simple things such as strings and individual numbers is already implemented by [https://docs.python.org/2/library/unittest.html#test-cases unittest].
+
+Data types to be checked:
 
  * raster map
@@ -249 +251 @@
 Most of the outputs can be checked with different numerical precision.
 
+We must have a simple guideline how to generate reference data. The output of G7:r.info for example is hardly comparable. It contains time stamps and user names that will differ for each test and platform. In addition the precision may be an issues between
+platforms for metadata values (min, max, coordinates). Hence the reference output must be parseable. One solution is, in case of metadata output (G7:r.info, G7:t.info, temporal modules in general), to require the output to be in shell format so that the reference check is able compare only these parts that contain values that will not change between test platforms. Alternatively we can use [https://docs.python.org/2/library/doctest.html#doctest.OutputChecker internal functions of doctest] which are able compare texts where part of the text is [https://docs.python.org/2/library/doctest.html#doctest.ELLIPSIS ellipsis].
+
 Resources:
  * http://grasswiki.osgeo.org/wiki/Test_Suite#Modules