[z3-five] maintaining the tests

[Martijn Faassen]

Hey,

Replying to myself:

Martijn Faassen wrote:

> This leads to another question -- test_security is definity not the 
> easiest thing to read. One instance of this is that for some reason 
> doesn't follow the standard ZopeTestCase pattern, and overrides setUp() 
> and tearDown() instead of using afterSetUp() and beforeTearDown(). It 
> also mixes in CleanUp. I tried to remove it to bring it to the 
> ZopeTestCase pattern, but of course I couldn't get things to work.

I also just discovered that test_security.py doesn't clean up after 
itself enough, causing subsequent tests to fail during 
unrestrictedTraverse(). I've disabled them from being picked up by the 
test runner for the time being.

[snip]
> I also suspect that if we make a separate product to support 
> the  security tests, along the lines of the way test_five does it, we 
> don't need this special casing.

I hope that doing this will also allow us to enable test_security.py again.

Regards,

Martijn