112: Six Principles of Readable Tests - David Seddon

"Code is read much more often than it is written." - Guido van Rossum
This is true for both production code and test code.

When you are trying to understand why a test is failing, you'll be very grateful to the test author if they've taken the care to make it readable.

David Seddon came up with 6 principles to help us write more readable tests.
We discuss these, as well as more benefits of readable tests.

David's 6 Principles of Readable Tests:

  1. Profit from the work of others
  2. Put naming to work
  3. Show only what matters
  4. Don’t repeat yourself
  5. Arrange, act, assert
  6. Aim high

Special Guest: David Seddon.

Sponsored By:

Support Test & Code : Python Testing for Software Engineers

Links:

Om Podcasten

Topics include automated testing, testing strategy, software engineering practices, packaging, Python, pytest, data science, TDD, continuous integration, and software methodologies. Also anything I think helps make the daily life of a software developer more fun and rewarding. Hosted by Brian Okken.