Le 10 juil. 09 à 20:03, Frank Niessink a écrit : > > If you have time, it would be nice to have a coverage report as one of > the build steps too. >
> First, 'easy_install coverage' to install coverage.py. Unfortunately, > > you need to fix a bug in it (see > http://bitbucket.org/ned/coveragepy/issue/11/html-report-does-not-report-on-all-code) > > . > If you change 'make unittests' into 'make coverage' the unittests will > be run and a HTML coverage report will be generated in > tests/coverage.out. > Okay, I'll look into that tomorrow. There is an issue with Fedora 11 that looks a lot like the MacOS one; from time to time unit tests pass but the Python process crashes at the end...
