RE: [pygame] pygame unittests

["Nicholas Dudfield" <ndudfield@xxxxxxxxx>]

@Marcus + Rene: 

Cheers, will take all that on board --> Write tests, add features as needed.

To be honest I am not that knowledgable re: properties and interfaces. I
vaguely remember reading about them once or twice.

A property is essentially a computed attribute (ie calls a function) with a
obj.property syntax? No argument calls?

Added to the reading list.

@Toni:

Yeah, I have read of doctest though never used it. I quite like the idea
behind it. Enforced upkeep of docs. Good stuff.

There are quite a few interesting python unittesting frameworks that seem
superior to unittest. I spent a few afternoons trawling through archives of
a python testing mailing list. A lot of interesting arguments / discussions
for this or that framework / method. After that I came away with the
impression that unittest is oldschool and thought about using something
else. 

But at the end of the day unittest is mature and ubiquitous. Better to focus
on writing tests than any shortcoming of the PyUnit framework.

Also, I am under the impression people want to stick with unittest. Been
wrong a zillion times before though.

-----Original Message-----
From: owner-pygame-users@xxxxxxxx [mailto:owner-pygame-users@xxxxxxxx] On
Behalf Of Toni Alatalo
Sent: Friday, May 30, 2008 8:32 PM
To: pygame-users@xxxxxxxx
Subject: Re: [pygame] pygame unittests

Nicholas Dudfield wrote:
> To that end I have been working on a unittest stub generator that uses
>   
(...)
> If we are only aiming at public methods this is a non issue. 
>   

do you know doctests, btw?
http://docs.python.org/lib/module-doctest.html

i've tested them (for Blender also, btw :)
and they have some interesting features.

~Toni