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

Vaclav Petras wenzeslaus at gmail.com
Mon Jan 21 14:26:22 PST 2019


On Mon, Jan 21, 2019 at 3:59 PM Markus Neteler <neteler at osgeo.org> wrote:

> On Mon, Jan 21, 2019 at 9:34 PM Vaclav Petras <wenzeslaus at gmail.com>
> wrote:
> > On Mon, Jan 21, 2019 at 3:08 PM Markus Neteler <neteler at osgeo.org>
> wrote:
> >>
> >> On Mon, Jan 21, 2019 at 1:48 AM Vaclav Petras <wenzeslaus at gmail.com>
> wrote:
> >> ...
> >> > Any reason for the file, i.e. can this be in the documentation?
> >>
> >> Not only because...
> >>
> >> > Or do you want a simpler example in doc and a link to the source code
> with more complex or ready-to-use examples?
> >>
> >> ... I need to be able to automatically call the script to test an
> installation.
> >> We are deploying GRASS GIS in a cloud environment (Openshift based)
> >> and cannot manually copy-paste scripts from the documentation.
> >
> >
> > OK, this raises the question if I should put the exact script I'm using
> at fatra.cnr.ncsu.edu to GRASS GIS code?
>
> Ah, in order to also run it directly, right?
>
> > I based the example in doc on that but considered the actual script as
> too specific (it needs to have the hardcoded paths anyway).
>
> Perhaps it might be the best to store the hardcoded paths in a
> separate config file which is "source"d by the test script?
>

That's a good idea. That way I we could actually run it directly without
storing the specific settings in the source code.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20190121/33a90ef8/attachment.html>


More information about the grass-dev mailing list