August 2025
Intermediate to advanced
294 pages
6h 59m
English
While working on Tunez, we’ve been doing lots of manual testing of our code. We’ve called functions in iex, verified the results, and loaded the web app in a browser to click around. This is fine while we figure things out, but it won’t scale as our app grows. For that, we can look at automated testing.
There are two main reasons to write automated tests:
To confirm our current understanding of our code. When we write tests, we’re asserting that our code behaves in a certain way. This is what we’ve been doing so far.
To protect against unintentional change. When we make changes to our code, it’s critical to understand the impact of those changes. The tests now serve as a safety net to prevent regressions in ...
Read now
Unlock full access