A word of warning
A great deal of customer-facing test tooling is a huge waste of time. The awkward, clunky, slow, brittle test steps tend to break a lot, are hard to debug, and rarely find real problems that matter. When Matt and Michael look at our customers and peers over the past two decades, few of them have really internalized the lessons from Chapter 2 of this book. There have been a couple of successes, but, on a bad day, we wonder if those are the exceptions and not the rule (https://techbeacon.com/app-dev-testing/6-common-test-automation-mistakes-how-avoid-them). Before we get started, let’s think for a moment about how most customer-facing test tooling works. It drives a user interface from the outside, perhaps through the operating system or the browser, simulating what a human does. Imagine an autonomous vehicle that did that with external video systems bolted on. Servomotors and gears control the steering wheel, gear shift, brakes, and accelerator, while a laptop...
