[GRASS5] Automated test-system for basic functionalities.

Sören Gebbert soerengebbert at gmx.de
Fri Jan 13 05:42:50 EST 2006

On Tuesday 10 January 2006 16:22, Radim Blazek wrote:
> On 1/10/06, Sören Gebbert <soerengebbert at gmx.de> wrote:
> > But if the test description is a shell script the user/dev will have more options to write tests.
> Do we need such options?
For the unit-test i think no, but for integration tests it may be usefull. 
(definition: if the unit is one grass module and the integration test the kombination of serveral modules)
> > We can define the test description in xml and write the framework in C/C++,
> > but in this case im not able write the framework (i dont have the time and the knowledge). :(
> No! I prefer something very simple. To use checksum is good idea.
> My idea was to have test location with some input maps in PERMANENT.
> Then the test descriptions could be a text file with GRASS commands
> and list of output data to be verified + checkums for that data.

I will try to make the core functionality of the testframework as simple and robust as i can.

Best regards
> Radim

More information about the grass-dev mailing list