homepage

This one is pretty involved. The tests might reach into the guts of the modules a bit too much, I'd be open to less invasive suggestions.

Is the patch against 3.4? I am not sure if we backport new test files.

Does all of the code for say, BdbTestCase.setUp, need to be repeated for each test method, versus being put in a .setUpClass method to be executed just once for all the methods in BdbTestCase.

A less invasive alternative could be to instrument Bdb with a subclass
that processes send-expect sequences. This is what does
http://code.google.com/p/pdb-clone/source/browse/Lib/test/test_bdb.py
This code could be adapted to run with python bdb.

I've updated the patch to consolidate some duplicated code. Unfortunately, I wasn't able to move anything to setUpClass without messing even more with the internals. I haven't had a chance to refine the code further based on xdegaye's suggestions, but I wanted to make sure I was getting feedback on the most up-to-date code.

IDLE's debugger needs multiple patches. It is based on bdb. So I want to be able to understand the bdb code and know that it is sound. The file is nearly devoid of docstrings, so I would like to add those first, probably in a separate patch. A first draft can be derived from the bdb doc. Docstrings will help in reviewing the patch.

I'll work on the bdb docstrings.

> The file is nearly devoid of docstrings, so I would like to add those first, probably in a separate patch.
Please move this new request for enhancement to a separate issue.

While I have previously done docstrings and tests together, I can see that for this issue, separation might be preferable. Cherl, can you open a new issue and re-title the PR? (I don't know if that will be sufficient to 'move' it, but I hope so.)

Moved to issue 30211 for docstrings.

Thanks Terry and Cheryl for splitting the issue :)

Wondering if it might make sense to use Mock in this patch?

PR 5217 adds the test.test_bdb module and provides a framework for adding more tests to the bdb module.
Added versions 3.6 and 2.7. This is consistent with what was done in issues #21916 and #25616 for example, but the main reason is that most bdb bug fixes need to be backported to the maintenance and 2.7 versions and should use the same test case whenever possible.

New changeset 3fe33043ee83d19e15551094fc1e0984617ded3c by Mariatta (xdegaye) in branch 'master':
bpo-19417: Add test_bdb.py (GH-5217)
https://github.com/python/cpython/commit/3fe33043ee83d19e15551094fc1e0984617ded3c

New changeset fdd8e8b4ffb68a4e8749bdc3b130fea7bbbf821e by Miss Islington (bot) in branch '3.7':
bpo-19417: Add test_bdb.py (GH-5217)
https://github.com/python/cpython/commit/fdd8e8b4ffb68a4e8749bdc3b130fea7bbbf821e

New changeset 424f3dafea16fbaee55a30903af2d6717f4d4a6b by Mariatta (xdegaye) in branch '3.6':
bpo-19417: Add test_bdb.py (GH-5217)
https://github.com/python/cpython/commit/424f3dafea16fbaee55a30903af2d6717f4d4a6b

New changeset 57e70d3802a2a78e638999c6923053c63fe373f8 by Miss Islington (bot) (xdegaye) in branch '2.7':
[2.7] bpo-19417: Add test_bdb.py (GH-5217) (GH-6156)
https://github.com/python/cpython/commit/57e70d3802a2a78e638999c6923053c63fe373f8