Before we can get into the nuts and bolts about how to do automated testing well, we have to understand what it means to do testing well. And for that, we need a guiding principle. 

Automated testing, like so many aspects of solving problems with software, is a path of mastery. You can forever get better and better at it, and the magnitude of potential benefits are unbounded. However, it will be difficult to impossible to continually make progress without some guiding light showing us what way to go. A well constructed guiding principle can do exactly that for us. It provides a semi-objective way to assess progress and help make choices along the way.

In this episode I synthesize the benefits we explored in the last episode with some observations about the essential nature of automated testing. From that I propose a guiding principle that should help us all agree on what is and is not good automated testing.

Timestamps

0:44 - definition

1:17 - as proof

2:23 - metacode

3:00 - recap of benefits

3:56 - The Guiding Principle

5:28 - summary

6:40 - next time

7:08 - outro

Related C&O Episodes:

• E036 - Surprising Benefits of Automated Testing - https://youtu.be/pBNzAB45_Hc

Hosted on Acast. See acast.com/privacy for more information.