Test and Docs: Hand in Hand
summary
Claims that tests can double as end‑user docs with a working prototype that records UI steps, captures screenshots and emits Markdown reports. Toolchain specifics include doc test prototype, uses Appium and can emit Espresso tests, and it integrates screenshots into docs usable by Jekyll. Demonstrations show recorded runs passing on an Android emulator, produced JUnit reports and static docs. Open source GitHub hosting and examples for WhatsApp Google Photos Intercom PayPal workflows are provided.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 0:23Disclaimer
- 1:01Emojis
- 1:33Apps for everybody
- 5:02Test for everything
- 5:45End user docs
- 6:04Online Health
- 6:35App Help
- 7:20Intercom
- 8:07Google Photos
- 8:47PayPal
- 9:29Problem
- 10:49Tests
- 11:24Test Failures
- 12:32Test Structure
- 13:18Espresso
- 13:43Espresso Examples
- 14:49Test Recorder
- 15:52Test that is readable
- 17:01Goals
- 17:34Docs Test
- 17:59Android Studio
related talks
38mDocs as Tests: A Strategy for Resilient Docs
37mKeeping trust: Testing documentation as part of a continuous integration process
18mExploration of tools, frameworks to take the pain out of mobile app testing!
39mTesting, Testing, 1, 2, NaN
44mTesting Documentation: Why So Technical?
39mIndustrialize your Android Tests: a Tools and Methods Cookbook
23mWhy testing is also a developer's problem
37mState of Android Testing in 2022