Changes between Version 41 and Version 42 of GSoC/2014/TestingFrameworkForGRASS


Ignore:
Timestamp:
Jun 27, 2014, 3:12:24 PM (10 years ago)
Author:
wenzeslaus
Comment:

Weekly report 6 (no formatting)

Legend:

Unmodified
Added
Removed
Modified
  • GSoC/2014/TestingFrameworkForGRASS

    v41 v42  
    587587
    588588[http://lists.osgeo.org/pipermail/grass-dev/2014-June/069609.html report email]
     589
     590=== Week 06 ===
     591
     5921. What did you get done this week?
     593
     594I've created a specialized functions to test output of modules such as r.info and r.univar against a reference set of values. This enables to test different properties of raster and vector maps and few other things (practically anything what is provided by some module as key-value pairs).
     595
     596I also added the MD5 check sum comparison of files. The functionality of Luca's g.compare.md5 is not yet available but it should be easy to add it once needed (some merge with the module should be then considered).
     597
     598The documentation is now updated, so although the framework is not integrated to GRASS yet, it is be now possible to write tests of GRASS modules which outputs raster and vector maps (tests of Python and ctypes function are in some limited way available from the beginning).
     599
     600I again worked on the ticket #2326 because of its importance. By few experiments I discovered that there is a lot of hidden errors at least in GUI which are visible with more strict API. However, I'm not sure if it is possible to use this more strict API in version 7.x, so for now I used the ideas to create module calling functions in testing framework (currently called gunittest package).
     601
     6022. What do you plan on doing next week?
     603
     604The plan is to start integration with GRASS and for the week after the plan is implementation of location switching for test. I think I will have to work on both these problems together.
     605
     6063. Are you blocked on anything?
     607
     608Not really but it would be very helpful now to have tests of actual modules to see limitations of my current implementation.
     609
     610http://trac.osgeo.org/grass/browser/sandbox/wenzeslaus/gunittest/testing.rst?rev=61021
     611http://trac.osgeo.org/grass/ticket/2326
     612http://trac.osgeo.org/grass/browser/sandbox/wenzeslaus/gunittest/gmodules.py?rev=61003
     613http://trac.osgeo.org/grass/wiki/GSoC/2014/TestingFrameworkForGRASS#Week06