[issue12681] unittest expectedFailure could take a message argument like skip does

Serhiy Storchaka added the comment: Such change would break a lot of existing interfaces. * addUnexpectedSuccess() has a single parameter. The change will add the second parameter and will break subclasses of TestResult. * addExpectedFailure() has two parameter. The change will add the third

[issue12681] unittest expectedFailure could take a message argument like skip does

Change by Irit Katriel : -- versions: +Python 3.11 -Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue12681] unittest expectedFailure could take a message argument like skip does

Changes by Robert Collins : -- nosy: +rbcollins ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue12681] unittest expectedFailure could take a message argument like skip does

R. David Murray added the comment: Thanks, Adam. I'm afraid it may be a while before Michael (or anyone else) gets a chance to review it and think about the issue some more. -- ___ Python tracker

[issue12681] unittest expectedFailure could take a message argument like skip does

Adam Collard added the comment: I've got a patch for this, but I'm a bit worried about the impact on the documented API. I've tried to do the best I could to minimize it through use of keyword-arguments but I'm a bit unsure about the change (and the docs too!) I hope this is useful to someone!

[issue12681] unittest expectedFailure could take a message argument like skip does

Changes by Adam Collard : -- nosy: +adam-collard ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue12681] unittest expectedFailure could take a message argument like skip does

Ezio Melotti added the comment: Maybe we could add an expected_issue(id) decorator to test.support. -- nosy: +ezio.melotti ___ Python tracker ___ ___

[issue12681] unittest expectedFailure could take a message argument like skip does

Michael Foord added the comment: Well, it would be nice for the Python test suite, maybe not so useful for external users of the api. Something for regrtest rather than unittest I think. -- ___ Python tracker ___

[issue12681] unittest expectedFailure could take a message argument like skip does

Barry A. Warsaw added the comment: It would be nice if expectedFailure took a bug number and printed a url to the tracker. -- nosy: +barry ___ Python tracker ___ __

[issue12681] unittest expectedFailure could take a message argument like skip does

Michael Foord added the comment: Well, expectedFailure could dispatch on the type of the argument, with different behaviour for strings and anything else (presumed to be a function / method). That would be inconsistent with the api for skipping though. (I'm not wild on the message argument to

[issue12681] unittest expectedFailure could take a message argument like skip does

Benjamin Peterson added the comment: Too late I'm afraid as expectedFailure not expectedFailure() is the decorator. -- nosy: +benjamin.peterson ___ Python tracker ___ __

[issue12681] unittest expectedFailure could take a message argument like skip does

Changes by Santoso Wijaya : -- nosy: +santa4nt ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue12681] unittest expectedFailure could take a message argument like skip does

New submission from R. David Murray : I think that it would be good for expectedFailure to take a message argument like skip does. My thought is that it would be printed both when it is triggered (the test fails as expected) so that one case from the verbose output why the test is expected to