Sunday 27 September 2009 — This is close to 14 years old. Be careful.
A beta of Coverage.py 3.1 is available. Coverage.py is a tool for measuring code coverage of Python programs, usually during testing. The big feature of 3.1 is that Python 3.1 is now supported.
Kits are available as source or as Windows installers from the coverage.py page on PyPI, and code is also available from the repository on bitbucket.
Significant changes in coverage.py since v3.0.1:
- Python 3.1 is supported. The same source kit works on both 2.x and 3.x.
- The “coverage” command now uses a sub-command syntax similar to source control systems. This will make new feature additions easier.
- Coverage results can be reported as a Cobertura-compatible XML file. Use the new “coverage xml” command. I’m looking for users who use Hudson or Sonar to ensure that this is working properly in all cases.
- Some users reported incorrect results due to using DecoratorTools, which fiddles destructively with the settrace function. TurboGears is a major example of code that wasn’t measured properly. The new --timid switch makes coverage.py operate simply enough that DecoratorTools doesn’t interfere with its operation.
- HTML coverage reports now have syntax-colored Python source.
Please try 3.1b1 and let me know what you think. Feedback is welcome in any way you like, but particularly good are tickets on bitbucket, or email on the testing-in-python mailing list.
Add a comment: