Vinícius Dantas added the comment: In the point of view of a tester, if it's an error, they will know right away it is a test case problem, not an assert problem. That makes debugging easier. It is also important to note that, if it's an AssertionError, we may add a message. While, if it is an error, no message would be displayed but the original Exception's.
As Selenium's example, as I said, was just a use case example. Finally, having the failure reason explicit is better than keeping it implicit. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29686> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
