[issue14265] Fully qualified test name in failure output

Change by Andrew Svetlov : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue14265] Fully qualified test name in failure output

Andrew Svetlov added the comment: New changeset 755be9b1505af591b9f2ee424a6525b6c2b65ce9 by Sam Ezeh in branch 'main': bpo-14265: Adds fully qualified test name to unittest output (GH-32138) https://github.com/python/cpython/commit/755be9b1505af591b9f2ee424a6525b6c2b65ce9 -- nosy:

[issue14265] Fully qualified test name in failure output

Sam Ezeh added the comment: The provided patch wasn't entirely compatible with the current upstream code. I used the patch file to apply the changes to `Lib/unittest/case.py`, resolved the remaining conflicts with the patches to the test files and amended existing tests for the library. I

[issue14265] Fully qualified test name in failure output

Change by Sam Ezeh : -- keywords: +patch pull_requests: +30218 pull_request: https://github.com/python/cpython/pull/32138 ___ Python tracker ___

[issue14265] Fully qualified test name in failure output

Change by Sam Ezeh : -- nosy: +dignissimus ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue14265] Fully qualified test name in failure output

Ethan Furman added the comment: Hopefully somebody on the core-mentorship list can move this forward by converting to a PR and reviewing. If @palaviv is still active the review itself will still be useful. -- assignee: michael.foord -> ethan.furman keywords: +easy -patch nosy:

[issue14265] Fully qualified test name in failure output

Aviv Palivoda added the comment: Included is a patch with the suggested change. I changed the TestCase.__str__ method to: return "%s (%s.%s)" % (self._testMethodName, strclass(self.__class__), self._testMethodName) instead of return "%s (%s)" % (self._testMethodName,

[issue14265] Fully qualified test name in failure output

Antoine Pitrou pit...@free.fr added the comment: Which failure message are we talking about? regrtest? unittest? -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14265 ___

[issue14265] Fully qualified test name in failure output

R. David Murray rdmur...@bitdance.com added the comment: I'm pretty sure Michael is talking about unittest. Doing the same for regrtest would be interesting but not as important. (When I run individual tests from the Python test suite I generally use -m unittest to do it.) --

[issue14265] Fully qualified test name in failure output

New submission from Michael Foord mich...@voidspace.org.uk: Somewhere in the failure message for tests Guido would like to see the fully qualified test name, suitable for copying and pasting into a test runner invocation for running just that test. -- assignee: michael.foord

[issue14265] Fully qualified test name in failure output

R. David Murray rdmur...@bitdance.com added the comment: +10 :) -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14265 ___