-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Il 07/03/2013 09:53, Victor Olaya ha scritto: > Hi all, > > I have been thinking about how to ease the process of creating unit > tests for SEXTANTE algorithms. Ideally, there should be (at least) > a test for each algorithm. I do not fancy the idea of automating > that
Hi Victor, thanks for that. I think the problem can be split in two: * checking that a module works * checking that it works well. The first one would simply mean that a module would produce an output (of the type expected); I think this check should be run automatically at every commit into the sextante code, to be sure nothing breaks badly. I think this should be very easy to implement, and could be done soon. Most errors will be spotted this way. Many less used modules can break without nobody noticing it. Your suggestion address the second issue, and is obviously better, but it will take longer to implement. So I would suggest to implement the first one soon, doing the second for a GSoC or other. All the best. - -- Paolo Cavallini - Faunalia www.faunalia.eu Full contact details at www.faunalia.eu/pc Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlE44rgACgkQ/NedwLUzIr5YAACeMocd4JkmO+NDQ9QbwM+PQrB8 V/0AoJVPbIcDJbCVyEbjpAGuzRGV1jfj =JrQh -----END PGP SIGNATURE----- _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
