Re: [Pyobjc-dev] Implementing custom setValue_forKey_

[Orestis M. <or...@or...>]

On 4 Apr 2009, at 20:52, Ronald Oussoren wrote:

>
> On 4 Apr, 2009, at 19:47, Orestis Markou wrote:
>
>> Woo my first bug! Should I file a ticket about it? If you give me a  
>> pointer on where it should live I may be able to write a test...
>
> I've already fixed in a simple testcase that triggers the bug.
>
> Ronald

Out of curiosity, how do you manage test runs that may crash? Is there  
a buildbot running PyObjC or do you just run the tests manually? We're  
looking to setup a buildbot to test PyObjC code and perhaps there's  
some insights you can share.

IME, PyObjC programs are a bit hard to test, for example, there's no  
easy way to cleanly launch and close an application. Of course, a lot  
of this has nothing to do with PyObjC but with Obj-C and Mac OS X.  
Another very annoying thing is having (for practical reasons) to do  
"from somewhere import *". I've also found that using mock[1] and its  
"patch" method, that monkey-patches a namespace lead to a bus error,  
which was very unusual. I'll see if I can reproduce that...

Any suggestions on testing PyObjC programs welcome!

Orestis

[1]: http://pypi.python.org/pypi/mock