Envisage core tests...

G'day,

I just noticed a checkin that added a 'SkipTest' to the 'test_remove_provider' test of the 
'provider_extension_registry_test_case'...

This test works just dandy for me, and since Envisage 3.x is developed TDD (and hence the tests get 
run almost by the minute when I am working on the code), it is *extremely* smelly to have a broken test!

Now I assume that the breakage you are seeing is caused by the way the tests are run (maybe a local 
resource issue?!?)... please let me know how to reproduce the problem and I will fix the tests 
accordingly...

In future, if you *think* any tests are broken in the Envisage core then please e-mail me before 
hacking in a SkipTest...

Martin