I should probably abandon the idea that the test suite will work either with Twisted's TestCase or the stdlib TestCase (unless I'm willing to actually start testing it against both continuously, which I'm not). So that probably means just using stdlib TestCase everywhere (I'd rather use Twisted's everywhere, but probably more people will be happy the other way :).
The way I'd prefer to do this is to have a base TestCase in OpenSSL which adds whatever features the OpenSSL test suite wants to use (like _Python23TestCaseHelper, but not a mixin).
For features that are too hard to implement for this to be worthwhile (eg temp file cleanup, probably), modifying the test_ methods themselves is probably sensible.
I should probably abandon the idea that the test suite will work either with Twisted's TestCase or the stdlib TestCase (unless I'm willing to actually start testing it against both continuously, which I'm not). So that probably means just using stdlib TestCase everywhere (I'd rather use Twisted's everywhere, but probably more people will be happy the other way :).
The way I'd prefer to do this is to have a base TestCase in OpenSSL which adds whatever features the OpenSSL test suite wants to use (like _Python23TestCa seHelper, but not a mixin).
For features that are too hard to implement for this to be worthwhile (eg temp file cleanup, probably), modifying the test_ methods themselves is probably sensible.