Re: [Pyobjc-dev] Testsuite adventures
Brought to you by:
ronaldoussoren
From: Ronald O. <ous...@ci...> - 2003-05-18 09:20:47
|
On Friday, May 16, 2003, at 11:44 Europe/Amsterdam, Dinu Gherman wrote: > Hi, > > I'm investigating a little bit the shape of the testsuite and > find it to be in a slightly undesirable state. I assume this is > because there is no global testing module which you could easily > run to execute all test modules anywhere in the source tree. So > I've written one such module, allTestsTogether.py, which gives > interesting results (please change the name to something like > alltests.py): > > [localhost:~/Desktop/pyobjc] dinu% python allTestsTogether.py > ..E....EEE.E..EEEEEE....EEE.E..EEEEE......................... > ...............E..E..EEEEE..E................................ > .2003-05-16 09:41:08.155 python[6095] *** -[NSBitmapImageRep > init]: selector not recognized................EBus error The changes I checked in earlier this week seem to fix most problems your seeing, there are 2 errors left related to the reuse of a class name (which the ObjC runtime doesn't support). The bus error is not fixed (yet). > After this investigation I'd like to know more about what the > PyObjC testing policy is? Maybe a topic for some part of the > documentation? We try to cover as much functionality as possible with unittests. We are getting closer and closer to that goal, but we are not there yet. I regulary run the unittests using the runalltests script. I also try to remember to add a unittest whenever I fix bugs, but I often forget to do that. Ronald |