Thinking of your tests as a software product
summary
Claims that a small set of end-to-end UI tests doubles development speed and cuts release anxiety, demonstrated by building an "app model" architecture: layered test cases, a reusable app model API, and a thin UI driver that wraps xcu tests. The platform at Dropbox moves from 20–30 line brittle scripts to readable steps, reduces flaky tests, and makes adding tests cheap after initial work; reaching ~100 tests required costly refactors but the system scales to teams of a few dozen engineers.
AI-written summary · about
chapters (9)
- 0:00The challenge of testing
- 5:29Improving testing at Dropbox
- 7:10The value of UI tests
- 9:38Initial testing struggles
- 12:02Treating tests as a product
- 15:48The app model architecture
- 20:06App model layer details
- 23:38Implementing the UI driver
- 29:40Conclusion and Q&A
