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 janssen
Recipients chasonr, christian.heimes, janssen
Date 2008-01-28.04:46:52
SpamBayes Score 0.00030648516
Marked as misclassified No
Message-id <4b3e516a0801272046m5d1b58dau5c487ad182031566@mail.gmail.com>
In-reply-to <1201489174.59.0.580429992019.issue1926@psf.upfronthosting.co.za>
Content
Yeah, it took me a couple of months to do a reasonable test case for the SSL
code.

Perhaps we could test against an existing NNTP server?  Like Google's?

Bill

On Jan 27, 2008 6:59 PM, Ray Chason <report@bugs.python.org> wrote:

>
> Ray Chason added the comment:
>
> It seems that I, or whoever writes any future test_nntplib.py, would
> have to understand how existing tests such as test_smtplib.py work.  It
> looks like that one is setting up some kind of miniature mail server and
> accepting a connection on localhost -- neat trick, binding a server
> socket to port 0 so it still works if you have a real mail server running.
>
> Anyway, getting good coverage isn't something I can bang out in an
> afternoon.  Class NNTPBase and its derivatives (I'm talking post-patch
> of course) have lots of methods and I want to cover them as well as
> possible.
>
> __________________________________
> Tracker <report@bugs.python.org>
> <http://bugs.python.org/issue1926>
> __________________________________
>
Files
File name Uploaded
unnamed janssen, 2008-01-28.04:46:52
History
Date User Action Args
2008-01-28 04:46:53janssensetspambayes_score: 0.000306485 -> 0.00030648516
recipients: + janssen, christian.heimes, chasonr
2008-01-28 04:46:52janssenlinkissue1926 messages
2008-01-28 04:46:52janssencreate