-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
Write unit tests for pdb module #73784
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
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? |
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. |
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 find_function(). They should be moved too. Note that there is a bug in find_function() (it opens a file with default encoding). Tests for internal functions don't free us from testing the same functionality as a part of high level functions. |
Please open an issue. |
And decorate this test class with test.support.cpython_only. |
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? |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: