You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The title is pretty self explanatory. It means that if you have an assertion with annotations, the AssertionError thrown will contain the instances of the annotations' classes.
The other day I was just thinking about how useless annotations in assertions are. It feels weird to allow such thing only so you can have the doc annotation there. I thought then: to solve the problem "they don't do anything", instead of disallowing them, why not make them actually do stuff?
The text was updated successfully, but these errors were encountered:
The title is pretty self explanatory. It means that if you have an assertion with annotations, the
AssertionError
thrown will contain the instances of the annotations' classes.The other day I was just thinking about how useless annotations in assertions are. It feels weird to allow such thing only so you can have the
doc
annotation there. I thought then: to solve the problem "they don't do anything", instead of disallowing them, why not make them actually do stuff?The text was updated successfully, but these errors were encountered: