Customer-Facing Tests
In previous chapters, we introduced the idea that testing can be programmer-facing or customer-facing. We also defined testing as a technical investigation into the state of the software. For this chapter, our first problem is likely to be figuring out what the test automation portion of customer-facing test automation means. To accomplish this, we’ll discuss the consequences of the idea and then list some patterns we have seen to make the approach successful.
In this chapter, we cover the following topics:
- A word of warning
- Human or machine—is it either/or?
- GUI automation patterns
- Designing your customer-meaningful test tool approach
- Specification by example
- Low-code and no-code test automation tools
- Batch- and model-driven development
The astute reader should finish the chapter with the ability to analyze a given user interface and determine methods to save time by offloading test effort onto the computer...
