Principles for Automated Testing

Published 📅: ....
Last modified 📝: ....

Share this post on BlueskySee discussion on Bluesky

This post is meant to be a living reference for common patterns and principles that I personally find important when working within an automated test suite.

Some of these may only apply to specific scenarios, some you may disagree with, but so far they've all proven in my own experience to be incredibly valuable to maintaining a large automated test suite for a long time and with a lot of contributors.

Creating a test should be incredibly easy

If you want to encourage that tests get written and that your code is generally well covered then it should be dead easy for any contributor to create a (well structured) test.