Refactoring: The use of unittest.py in the test suite

[GoogleCodeExporter]

Currently the test suite uses unittest.py Tester classes to test PyGraphics. 

Problem:
If this is intended to be read by 108 students it may be overwhelming

Possible Solutions:
A) Convert it to a nose test suite
B) Implement our own test interface that is simpler to read (perhaps not as
informative)
C) Leave it as it is

Expected Amount of Work:
A) about 1 full day
B) Depends on what is expected of our own interface, but probably longer
than A)
C) No extra work

Ideas?

Original issue reported on code.google.com by C.J.Madd...@gmail.com on 6 May 2008 at 4:46

[GoogleCodeExporter]

Decision was made by paul and chris to go ahead with converting it to nose.

Original comment by C.J.Madd...@gmail.com on 6 May 2008 at 5:43

• Changed state: Started

[GoogleCodeExporter]

I just spoke to Paul about this and I agree.  One thing you should keep in mind 
is that you'll want to be able to 
run the tests in batch (as the test suite gets larger and is spread across 
multiple files).

Original comment by campbell...@gmail.com on 6 May 2008 at 5:54

[GoogleCodeExporter]

Sounds good, I'll convert TestExecute to a batch tester than runs all the other 
modules.

Original comment by C.J.Madd...@gmail.com on 6 May 2008 at 9:26

[GoogleCodeExporter]

Test suite is converted to nose, and it includes a batch testing module, 
TestExecute.

Original comment by C.J.Madd...@gmail.com on 7 May 2008 at 6:35

• Changed state: Fixed