Assertion libraries can be considered as mini-DSL’s that make automated tests more readable. When a team of devs make their choice, they usually judge on API preference. While it’s very important to have readable tests, the API should never be the deciding factor. What truly separates a good assertion library is the quality of its failure messages. The more actionable these messages, the faster you’ll diagnose the cause of failing tests.
