Message289169
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. |
|
Date |
User |
Action |
Args |
2017-03-07 15:55:36 | viniciusd | set | recipients:
+ viniciusd, rhettinger, r.david.murray, serhiy.storchaka |
2017-03-07 15:55:36 | viniciusd | link | issue29686 messages |
2017-03-07 15:55:36 | viniciusd | create | |
|