Changes between Version 36 and Version 37 of GSoC/2014/TestingFrameworkForGRASS


Ignore:
Timestamp:
06/13/14 10:06:55 (10 years ago)
Author:
wenzeslaus
Comment:

add pep257 to static analyses

Legend:

Unmodified
Added
Removed
Modified

  • GSoC/2014/TestingFrameworkForGRASS

    v36 v37  
    243243|| [https://pypi.python.org/pypi/mccabe McCabe complexity checker] || code [http://en.wikipedia.org/wiki/Cyclomatic_complexity cyclomatic complexity] || ||
    244244|| [https://pypi.python.org/pypi/flake8 Flake8] || combines !PyFlakes, pep8, and mccabe || yes || ||
     245|| [https://github.com/GreenSteam/pep257 pep257] || docstring style ([http://legacy.python.org/dev/peps/pep-0257/ PEP257]) || no || ||
    245246
    246247The determining code coverage of the tests must be done during testing. Speaking about Python, some more advanced testing frameworks includes code coverage tools in them, namely [http://nedbatchelder.com/code/coverage/ coverage]. Since `unittest` does not include `coverage`, GRASS will have to incorporate `coverage` into its testing framework. The basic usage is rather simple. If we consider that all is running in one Python process, we can just put the following (rather messy) code into some module which will be loaded before the tests will start (the main invoking script would be of course the best place):