Summary

This chapter introduced customer-facing test tooling. After a warning about the failure rate of such approaches, we dove in, explaining the patterns that make good user interface test tooling, how to move toward specification by example, and model-driven and low-code test tooling approaches. This should have given you several patterns for test tooling, along with the ability to analyze your existing software and select the best tooling approach: including no tooling at all.

So far, we’ve only talked about testing the features of the software. Type in some values and make sure you see a specific result. That doesn’t deal with the issue of multiple simultaneous users, foreign languages, the speed of the results, security, and so on. We view all of these as risks to the product, which may be within the scope of this book. In Chapter 5, we talk about these more specialized forms of software testing.