Proposals:Increasing ITK Code Coverage: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
(New page: __TOC__ = Motivation = ITK currently has a 804% code coverage. This means that about 30,000 lines of code are not tested. We could significantly increase the code coverage of the toolk...) |
|||
Line 12: | Line 12: | ||
It has been pointed out that the current testing infrastructure of ITK impose a high threshold of effort on contributors of new tests | It has been pointed out that the current testing infrastructure of ITK impose a high threshold of effort on contributors of new tests | ||
Suggestions for improving the testing system to make easier for contributors to introduce new tests include | |||
== Boost Test == | |||
Suggested by Steve Robbins | |||
* http://www.boost.org/doc/libs/1_37_0/libs/test/doc/html/index.html | |||
=== How it could work === | |||
== UnitTestCpp == | |||
Suggested by Mathieu Malaterre | |||
* http://unittest-cpp.sourceforge.net/ |
Revision as of 15:38, 29 December 2008
Motivation
ITK currently has a 804% code coverage.
This means that about 30,000 lines of code are not tested.
We could significantly increase the code coverage of the toolkit, and in the process reduce the number of hidden bugs, by asking volunteers to adopt particular classes and write additional tests for increasing their code coverage. This could be done at the image of the "Adopt a Bug" program.
Infrastructure
It has been pointed out that the current testing infrastructure of ITK impose a high threshold of effort on contributors of new tests
Suggestions for improving the testing system to make easier for contributors to introduce new tests include
Boost Test
Suggested by Steve Robbins
How it could work
UnitTestCpp
Suggested by Mathieu Malaterre