#3771: Run tests on Travis
--------------------------+-------------------------
Reporter: pmav99 | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone:
Component: Tests | Version: svn-trunk
Resolution: | Keywords:
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Comment (by wenzeslaus):
Replying to [comment:7 sbl]:
> Another relevant issue are test datasets, it seems.
As for (older) full and (newer) basic version of NC SPM, I think
nc_spm_full_v2alpha solves it //for now// (not ideal, but works). Making
nc_spm_full_v2alpha work is a good goal for the Travis runs now.
However, please also note the idea of different sample datasets, i.e.
other than NC SPM (old/full or new/basic or full v2). Please see: GRASS-
dev: Testsuite: script for easier use of test framework
https://lists.osgeo.org/pipermail/grass-dev/2019-January/091011.html
There are different approaches how to handle the different datasets in
tests and by the runner, but idea is 1) to make easy to write very
specific tests, 2) to test in different conditions like latlon GRASS
Location, and 3) to have tests which run in any GRASS Location and/or
without any data (so you can e.g. do `make test` without getting 100 MB of
sample data).
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3771#comment:22>
GRASS GIS <https://grass.osgeo.org>
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
