Tests That Don't Lie, Part 1: Readability and DSL

Originally published on my blog: https://camilyed.github.io/en/tests-that-dont-lie/ In this article, I want to share how I approach writing tests that are not there only to increase so-called code coverage, but give me confidence that after deploying a new feature, it works according to the original assumptions. Readability Let's start with the basics. If a test does not clearly communicate what is being tested and why it failed, then all the technology around it becomes unnecessar