[GRASS-dev] Re: 6.4.0 -ending story

[Tim Michelsen]

>> (everyone needs to test the heck out of it now of course)
>>   
> Suggested testing in spearfish:
> start with the reduced archsites vector provided by Michael, 11 points:
> https://trac.osgeo.org/grass/attachment/ticket/660/archsites11.zip
> 
> next the full archsites map, 25 points, then bugsites, 90 points
> 
> In the North Carolina dataset, you could test with elev_lid792_bepts,
> 118,716 points
> 
> If everything is fine so far, then generate 3 million random points and
> test that. Be aware that the output vector will be very large if area
> output is requested, rather use v.delaunay -l to get only lines.
> 
> In all test, v.delaunay should be run with --verbose in order to be able
> to follow the steps. The Delaunay triangulation should always finish
> within seconds, for millions of points < 1 min, whereas topology
> building can take some time.
Could this testing be automised?
There could be a Menu entry in the Help menu of the GUI:

-> Contribute
	-> Test GRASS
	-> Write WIKI documentation

When the user hits "Test GRASS" a series of tests is run an logged to a
file.
This could be sent to the developer mailing list or entered in trac
somewhere.

Just an idea.