Espresso Patronum: The Magic Of The Robot Pattern
summary
Claims that applying the robot pattern to Espresso tests turns verbose, brittle UI specs into concise, maintainable actions and assertions; demonstrates on a sample registration form example that tests read like plain steps, chainable via a builder pattern, and survive layout changes by updating one robot class. Shows better failure diagnostics and HTML screenshots using Spoon and Falcon, links a working GitHub demo, and reports that the approach noticeably reduces test churn and debugging time.
AI-written summary · about
chapters (36)
- 0:00Intro
- 2:03Three Classes To Know
- 2:19View Matchers
- 3:10ViewActions
- 3:35ViewAssertions
- 4:03Espresso Cheatsheet
- 4:38Espresso Example
- 6:24Sample Project
- 7:30Test Successful Registration
- 9:05Test A Missing Field
- 9:50One More Negative Test
- 10:17All Together
- 11:10The Problem
- 11:59No Separation Of Concerns
- 13:23Introducing Robots
- 15:10Usage
- 15:56Define ViewMatchers
- 16:23Each Action As A Method
- 18:27One Robot Per Screen
- 19:55Benefits
- 22:19Better Test Reporting Using Spoon & Falcon
- 23:46Example Spoon Report
- 24:20When To Take Screenshots
- 25:21Why screenshots?
- 25:50Console Output
- 26:38Spoon Output
- 27:17See Steps Taken
- 27:55Diagnose Failures - Stack Trace
- 29:01Diagnose Failures - Clear Image
- 29:21Learn More
- 30:01Adding Screenshots To Our Robot
- 30:49Why did we need a robot?
- 31:47Let's Add To It
- 32:33Registration Robot
- 32:56User ProfileRobot
- 34:07Recap
related talks
26mEspresso Patronum - The Magic Of The Robot Pattern
42mRock-Solid UI and Instrumentation Testing
48mDesign patterns to boost your test automation
38mEspresso, beyond the basics
43mUI testing is so easy - said no developer ever
44mEfficient testing UI Android apps by example
42mZero to hero in UI testing
36mLiving on crotches or UI Automation antipatterns