This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients Arfrever, giampaolo.rodola, janssen, loewis, pitrou
Date 2010-05-05.19:13:31
SpamBayes Score 1.0502567e-05
Marked as misclassified No
Message-id <1273086956.3499.9.camel@localhost.localdomain>
In-reply-to <4BE1BFD5.5040000@v.loewis.de>
Content
> Notice that we should *not* test OpenSSL - hopefully, they have their
> own test suites. Instead, we should only test the Python integration of
> OpenSSL. Therefore, we should only write test cases that work
> independent of the OpenSSL version (except when some API that we want to
> test is not available in older OpenSSL versions, in which case a
> testable way for that absence should be added when the API gets added).

I agree that these tests are more integration tests than unit tests;
however, they are useful in exercising the code and options we provide
(otherwise we wouldn't know whether e.g. PROTOCOL_TLSv1 really does what
it claims to do).

I think we can simply skip these tests in maintenance branches, where we
don't provide the necessary API to make them pass reliably.
History
Date User Action Args
2010-05-05 19:13:33pitrousetrecipients: + pitrou, loewis, janssen, giampaolo.rodola, Arfrever
2010-05-05 19:13:31pitroulinkissue8629 messages
2010-05-05 19:13:31pitroucreate