I’ve never tried the GRASS test suite, but thought it could be a better way to check binary builds than the ad hoc tests I make now. But I’m not sure how to use it. I looked at the GRASS WIKI but everything about the test suite has been deprecated, even thought it still ships with the GRASS code base.
Is it still in use?
The GRASS gunittest page seems to be about a way to test individual modules, or to test changes to the source code.
My goal is to test a binary to make sure that things work properly before I distribute.
Any advice?
Michael
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University
voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
Hi Michael,
the GRASS gunittest framework is exactly what you are looking for. Please have a look at its excellent documentation:
https://grass.osgeo.org/grass71/manuals/libpython/gunittest_running_tests.html
https://grass.osgeo.org/grass71/manuals/libpython/gunittest_testing.html
However, the test coverage is not very high for raster and vector modules. Feel free to implement new tests for all modules that you would like to have tested.
Here is a recent test run, that shows all modules that were tested:
http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2016-05-24-07-00/report_for_nc_basic_spm_grass7_nc/testfiles.html
Best regards
Soeren
···
2016-05-31 23:08 GMT+02:00 Michael Barton <Michael.Barton@asu.edu>:
I’ve never tried the GRASS test suite, but thought it could be a better way to check binary builds than the ad hoc tests I make now. But I’m not sure how to use it. I looked at the GRASS WIKI but everything about the test suite has been deprecated, even thought it still ships with the GRASS code base.
Is it still in use?
The GRASS gunittest page seems to be about a way to test individual modules, or to test changes to the source code.
My goal is to test a binary to make sure that things work properly before I distribute.
Any advice?
Michael
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University
voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Thanks Sören. I am thinking of something I can run to make sure that a selections of vital components work.
Michael
···
2016-05-31 23:08 GMT+02:00 Michael Barton <Michael.Barton@asu.edu>:
I’ve never tried the GRASS test suite, but thought it could be a better way to check binary builds than the ad hoc tests I make now. But I’m not sure how to use it. I looked at the GRASS WIKI but everything about the test suite has been deprecated, even thought it still ships with the GRASS code base.
Is it still in use?
The GRASS gunittest page seems to be about a way to test individual modules, or to test changes to the source code.
My goal is to test a binary to make sure that things work properly before I distribute.
Any advice?
Michael
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University
voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev