id summary reporter owner description type status priority milestone component version resolution keywords cc cpu platform 2105 Missing guidelines for testing wenzeslaus grass-dev@… "I miss any kind of guide how to create test. This applies for the main source code and the addons, C/C++ and Python, modules and code itself. There are tests of temporal modules but it is not currently described anywhere how they are organized. There is also a `testsuite` directory in trunk but it is not maintained. I've also noticed some tests running during compilation but I was never able to find out what it is. Some Python functions can be tested using `doctest` and Python developers usually know how to use it. However, it is not clear how to ensure calling from make. There is a page about the test framework we wish to have: * http://grasswiki.osgeo.org/wiki/Test_Suite But since it does not exists the page creates just confusion. There is also a mailing list about testing: * http://lists.osgeo.org/mailman/listinfo/grass-qa But it is not active. ''We probably also miss the testing infrastructure itself but that's another bigger ticket. But some things exists already, so we can use them.'' ''Maybe, we need Tests component in Trac?''" task closed normal 7.2.0 Tests svn-trunk fixed testing, tests, PyUnit, doctest, testsuite Unspecified All