[GRASS-dev] Testsuite: script for easier use of test framework

Vaclav Petras wenzeslaus at gmail.com
Wed Jan 16 13:04:42 PST 2019

On Wed, Jan 16, 2019 at 12:00 PM Markus Neteler <neteler at osgeo.org> wrote:

> @Vaclav Petras
> Maybe a workaround for the online test system at
> http://fatra.cnr.ncsu.edu/grassgistests/summary_report/
> ?

Hi Markus,

the reason I didn't do that was I was hoping we either decide which one to
use or release a new version of full NC SPM with the names from basic (we
were quite close to it at one point :-).

If I recall correctly, fatra.cnr.ncsu.edu was originally using the full
dataset for maximal variability, then I switched to basic because that was
what was applicable also for the piemonte_utm32_wgs84_grass7 dataset (which
hides under stdmaps link). This all goes back to the idea of testing
framework using different datasets:

1) full NC SPM (marked nc in lib/python/gunittest/multirunner.py and at
2) any Standardized Sample Datasets [1] (marked stdmaps; fatra uses
piemonte as an example).
3) any dataset (marked all; fatra uses an empty XY loc)

This marking is not part of the tests. I never had time to implement that.
Part of the mechanism is already in place, although I think there needs to
be some clarification on specifying tests which can run in any location (a
"universal" test) versus running all tests regardless of their specified

I changed the location on fatra to full NC SPM and did the rename as you
suggested. I don't know how many tests does this affect, but in any case
tomorrow we will know if I at least set the things correctly.


[1] https://grasswiki.osgeo.org/wiki/GRASS_GIS_Standardized_Sample_Datasets
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20190116/97fd9e82/attachment.html>

More information about the grass-dev mailing list