Use test coverage analysis tools to determine how well tested Plone 3 is

[GoogleCodeExporter]

Various tools exist to analyst how well an automated test suite covers a 
particular code base. The 
Zope test runner includes a basic coverage tool.

The task: Find an appropriate coverage testing tool for Python and use it on 
Plone's unit test suites 
(make sure to include tests in dependent packages as well). Produce a report 
outlining how you 
performed the tests, and suggest where code coverage could be improved.

Original issue reported on code.google.com by optil...@gmail.com on 19 Nov 2007 at 10:43

[GoogleCodeExporter]

Original comment by l...@gmail.com on 27 Nov 2007 at 7:00

• Changed state: o
• Added labels: 3-day

[GoogleCodeExporter]

Original comment by l...@gmail.com on 27 Nov 2007 at 7:02

• Changed state: Open

[GoogleCodeExporter]

now, what is it exactly that i'm trying to test? (I'm more than ready to accept 
the 
task, I just need some solid clarification on what I will be doing)

Original comment by hgama...@gmail.com on 2 Dec 2007 at 4:04

[GoogleCodeExporter]

Are you familiar with automated testing techniques (aka "unit testing" and 
"functional testing")? If not, do a bit of 
research first - http://plone.org/documentation/tutorial/testing may be a good 
starting point.

This task specifically refers to the use of automated tools that determine how 
much of the codebase is covered 
by automated tests. There is one (the --coverage option) that is part of 
Plone's standard test runner (see tutorial 
above), but there may be other, more appropriate ones for Python - up to you.

Original comment by optil...@gmail.com on 2 Dec 2007 at 11:54

[GoogleCodeExporter]

Original comment by mw4...@googlemail.com on 23 Jan 2008 at 11:35

• Changed state: deleted