Wrapping Up

Testing Elixir — by Andrea Leopardi, Jeffrey Matthias (19 / 80)

👈 Isolating Code | TOC | Chapter 2 Integration and End-to-End Tests 👉

After writing our first tests, we dug into how to define the scope of a unit test. We then explored the tools ExUnit provides us to organize our tests, rounding out our exploration with ways to design our code to be more testable: refactoring to pure functions or leveraging dependency injection. The foundation we’ve created — organizing test files, understanding the stages of a test, combining list comprehensions with assertions, and designing our code to be testable — will serve as a starting point for all of the additional concepts in this book.

In the next chapter, we’ll expand the scope of our testing black box through integration testing. You’ll see how most of the patterns can be scaled when testing across large parts of the application.

Footnotes

Copyright © 2021, The Pragmatic Bookshelf.

👈 Isolating Code | TOC | Chapter 2 Integration and End-to-End Tests 👉

Related posts:

Addiction is complicated, which is why, in many cases, you might actually be suffering from a variety of addictions and disorders at once. You might have a mental health disorder that leads to a…

A truly fine service-learning project — now in progress — from CWI Summer EAST alum Kimby Heil’s students in Trenton, NJ. Kimy’s students are also currently working on an article for Community Works…

This next test is very simple. First, let’s take a look at the code in our Users module. We used “Read” in the section header to keep it in line with CRUD, but you’ll notice that we prefer to call…