Increase unit test coverage

[GoogleCodeExporter]

All Crunchy .py files should have a corresponding .txt files containing
unit tests - even if it's only a stub.   When this is done, we can have
more specific test tasks.

Original issue reported on code.google.com by andre.ro...@gmail.com on 12 Dec 2007 at 2:25

[GoogleCodeExporter]

Change type to use new "test" type.

Original comment by andre.ro...@gmail.com on 12 Dec 2007 at 2:28

• Added labels: Type-Test
• Removed labels: Type-Task

[GoogleCodeExporter]

Test files now use .rst format.  With the latest changes made, using 
"interface.py",
it should be easier to write tests files, at least for plugins.

Original comment by andre.ro...@gmail.com on 30 Dec 2007 at 9:50

[GoogleCodeExporter]

This is covered by Tao's SoC project.

Original comment by johannes...@gmail.com on 23 Apr 2008 at 2:01

• Added labels: Maintainability

[GoogleCodeExporter]

We should come close to 100% (unit) test coverage for release 1.0.  Adding a 
label to
reflect this.  I will start working on unit tests again in a few days, 
complementing
Tao's work.

Original comment by andre.ro...@gmail.com on 3 Jun 2008 at 11:00

• Added labels: Milestone-Release1.0

[GoogleCodeExporter]

Task too monumental for 1.0 - we can't wait for the delay.  Removing any 
milestone label.

Original comment by andre.ro...@gmail.com on 27 Jun 2008 at 9:56

• Removed labels: Milestone-Release1.0

[GoogleCodeExporter]

This is probably another thing I should look at, in order to get abck into "the 
zone".

Original comment by johannes...@gmail.com on 19 Aug 2009 at 4:45