Comment 7 for bug 419691

@mwhudson
 - we need to do something to do with resources that can't be cleaned up. The zope test runner runs these in subprocesses.

You could thunk into subunit for those. Alternatively we could just clean them up - 'cannot' is a very strong statement.

 - we need to think what to do about the layers that have testSetUp and testTearDown methods. possibly resources that are always dirty?

Yes, that would work, or perhaps child resources that go dirty and the parent doesn't.

 - similarly, some of our layers check invariants. how do we do that with testresources?

Point me at some code, I'll have a think.

 - zope.testing at least used to ignore any special suite you specified for your tests, which would mean testresources' OptimizingTestSuite would be useless during a transition.

It rearranges things as it pulls the layers out. I have in my head an adapter for testresources to honour layers-as-resources, which would permit nuking zope.testing's layer support on day one.

 - we need to define the resources launchpad tests need and come up with a transition strategy.

I think an incremental approach might be easier to deploy.