[GRASS-dev] [GRASS GIS] #2105: Missing guidelines for testing

GRASS GIS trac at osgeo.org
Wed Nov 13 08:57:30 PST 2013


#2105: Missing guidelines for testing
--------------------------------------------------------+-------------------
 Reporter:  wenzeslaus                                  |       Owner:  grass-dev@…              
     Type:  task                                        |      Status:  new                      
 Priority:  normal                                      |   Milestone:  7.0.0                    
Component:  Tests                                       |     Version:  svn-trunk                
 Keywords:  testing, tests, PyUnit, doctest, testsuite  |    Platform:  All                      
      Cpu:  Unspecified                                 |  
--------------------------------------------------------+-------------------

Comment(by wenzeslaus):

 Some software projects require to have a test for each closed ticked,
 fixed bug or commit. I'm wondering how to do it for platform dependent or
 system configuration specific issues such as r58200 discussed at
 [http://lists.osgeo.org/pipermail/grass-dev/2013-November/066277.html
 GRASS-dev]. Maybe in the same way as GUI part of the GUI can be tested,
 i.e. document with steps what to do (how to reproduce).

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/2105#comment:8>
GRASS GIS <http://grass.osgeo.org>



More information about the grass-dev mailing list