Test automation on the living room devices
summary
Video already makes ~60% of internet traffic and Netflix alone uses ~15%; smart TV fragmentation is extreme (Samsung 32% share but dozens of models per year), so automation needs device-specific hooks not just web tools. Current options split into object-based APIs (Espresso/XCUITest/Appium) and image-based captures with limits — DRM blocks screenshots and HDMI grabbing has legal issues, so camera rigs or IR/HDMI-CEC injectors are common. Appium 2.0 adds a driver ecosystem and plugins; sweetest is releasing an Appium 2.0 driver and a public device lab (October).
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:10What is a living room device
- 2:13Why should we care
- 4:32New vendors
- 7:22Device fragmentation
- 10:06Smart TV problems
- 11:54Smart TV solutions
- 14:26Installing apps
- 15:45Screen recording
- 19:41User input emulating
- 22:56Keyboard input
- 26:10Running assertions
- 28:09Tips
- 33:53What is next
- 35:56Appium 20 ecosystem
- 38:08Sweetest and Apple
- 39:50Questions
related talks
30mAppium For Couch Potatoes
40mAppium For Couch Potatoes - An HbbTV Driver
43mMobile Automation State in 2019
18mExploration of tools, frameworks to take the pain out of mobile app testing!
43mUnlocking New Testing Capabilities with Espresso Driver
57mAppium: Automation for Apps
46mHow we took Appium to 11 platforms
30mMobile Test Automation at the BBC: Then, Now and Next
