[Pyobjc-dev] Testing

[<bb...@ma...>]

On Wednesday, October 30, 2002, at 11:21 AM, Ronald Oussoren wrote:
> On Wednesday, Oct 30, 2002, at 16:29 Europe/Amsterdam, bb...@ma... 
> wrote:
>> (Ronald:  I feel that the test/ directories should ship with the 
>> 'binary distribution' in the location that they are in.   Normally, 
>> the python distribution ships with the unittests and it has been 
>> incredibly helpful to be able to wander into an alien python 
>> installation, run the unit tests, and see exactly what was built into 
>> the distribution in a working fashion.... for us, it means that the 
>> user community can easily validate whether PyObjC still works after a 
>> system update from Apple.)
>
> Agreed. I've noticed how usefull this is w.r.t. testing of prereleases 
> of MacPython.
>
> Adding a script in that runs all tests would also be usefull. This 
> would have to  run all test_*.py scripts in a new interpreter: It is 
> highly likely that some tests will depend on having some modules 
> loaded or not loaded (e.g. testing if importing AppKit makes available 
> extra categories on a number of Foundation classes).

I have a test_all.py in my local workarea that I'm working on as a "run 
all tests" solution.  I hadn't thought of running each test in a new 
interpreter, but that certainly makes a lot of sense.

It also solves another problem.  Apple failed to ship the unit tests 
with their distribution of Python [bug filed] and, as such, the drivers 
for running all tests in a directory are missing.   I was going to 
figure out how to do another ssl/readline style 'add this missing piece 
to the Apple supplied python' package, but-- given that it doesn't 
support new interpreters anyway-- it wouldn't solve the problem at hand.

I'll work up a solution for running all the tests and commit it later 
today [tonight].

b.bum