When coding with ScalaTest, many people end up using only the very basic matchers (equal, be), since invariably it’s faster to just write the tests out than open up the docs.
Unfortunately, this leads to the tests - deprived of the more expressive features of ScalaTest - ending up less self-documenting, having poorly-worded assertions (“true does not equal false”), or just being flat out incorrect.
This talk will demonstrate the most important matchers, and will highlight some ScalaTest quirks, hopefully allowing you to avoid subsequent head-scratching debug sessions.
voted / votable