[issue34514] assertEqual doesn't use maxDiff when comparing dictionaries
New submission from Victor Engmark : According to the documentation `assertDictEqual()` "will be used by default to compare dictionaries in calls to assertEqual()." Great, since `maxDiff` applies to assertDictEqual(). However, `maxDiff` doesn't apply to `assertEqual()` when comparing dictionaries. -- components: Tests messages: 324140 nosy: Victor Engmark2 priority: normal severity: normal status: open title: assertEqual doesn't use maxDiff when comparing dictionaries type: behavior versions: Python 3.6 ___ Python tracker <https://bugs.python.org/issue34514> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32927] Add typeshed documentation for unittest.TestCase._feedErrorsToResult and ._outcome
New submission from Victor Engmark <victor.engm...@gmail.com>: Until and unless #32926 is fixed it would be good to be able to type inspect code which uses the currently least hacky way to inspect the result of the current test [1]. This requires the use of TestCase._feedErrorsToResult and TestCase._outcome. [1]: https://stackoverflow.com/a/39606065/96588 -- messages: 312672 nosy: Victor Engmark priority: normal severity: normal status: open title: Add typeshed documentation for unittest.TestCase._feedErrorsToResult and ._outcome type: enhancement ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32927> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32926] Add public TestCase method/property to get result of current test
New submission from Victor Engmark <victor.engm...@gmail.com>: The community has come up with multiple hacks [1] to be able to inspect the current test result in tearDown (to collect more expensive diagnostics only when the test fails). It would be great to have a documented and simple way to check whether the test currently in play was successful. To be clear, TestCase.wasSuccessful() is not useful in this case, since it only reports whether all tests run so far were successful. [1] https://stackoverflow.com/q/4414234/96588 -- messages: 312671 nosy: Victor Engmark priority: normal severity: normal status: open title: Add public TestCase method/property to get result of current test type: enhancement ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32926> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
