[issue29598] Write unit tests for pdb module

Batuhan added the comment: PR 218 is closed and this issue looks like just created for that PR. If that PR is closed and there are nothing to do with this issue, maybe this can also be closed? -- nosy: +BTaskaya ___ Python tracker

[issue29598] Write unit tests for pdb module

Serhiy Storchaka added the comment: And decorate this test class with test.support.cpython_only. -- ___ Python tracker ___

[issue29598] Write unit tests for pdb module

Xavier de Gaye added the comment: > Note that there is a bug in find_function() (it opens a file with default > encoding). Please open an issue. -- ___ Python tracker

[issue29598] Write unit tests for pdb module

Changes by Serhiy Storchaka : -- nosy: +inada.naoki ___ Python tracker ___ ___

[issue29598] Write unit tests for pdb module

Serhiy Storchaka added the comment: It would be better to move all tests for internal functions in separate TestCase class. It should be clear that this is testing of implementation details and we are free to change tests when change the implementation. There are some tests for

[issue29598] Write unit tests for pdb module

Changes by Roundup Robot : -- pull_requests: +182 ___ Python tracker ___

[issue29598] Write unit tests for pdb module

Xavier de Gaye added the comment: Please use one single PR only when the tests are focused on a single topic and can be collected in their own class. When the tests are focused on breakpoints for example. -- nosy: +xdegaye ___ Python tracker

[issue29598] Write unit tests for pdb module

New submission from Artem Muterko: I want to write unit tests for pdb module of stdlib. Should I create one pull request for entire module or should I split work into several pull requests? -- ___ Python tracker

[issue29598] Write unit tests for pdb module

Changes by Artem Muterko : -- components: Tests nosy: Artem Muterko priority: normal severity: normal status: open title: Write unit tests for pdb module versions: Python 3.7 ___ Python tracker