Readable. Stable. Maintainable. E2E Testing @ Facebook
summary
Facebook replaces raw WebDriver scripts with a component-based, page-object style framework that makes E2E tests declarative and typed, hiding find/click sleeps and XPath. A provisioning service called OneWorld gives ready simulators/emulators and yields ~10x speedups plus video and system logs. Tests express intent (e.g., scroll until story.author matches X) and the framework guarantees no stale element references, automatic re-querying and uniqueness checks, producing a declarative API that improves readability, reuse and stability.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:59Outline
- 4:00Growth of WebDriver Tests
- 7:17Hard to Read and Write
- 9:17Key Concepts
- 14:07Nested Components
- 16:37Page Objects
- 17:37Composing Tests
- 19:36How Does It Work
- 21:48How Did We Fix the Bad?
- 22:22Summary
related talks
38mTesting and moving fast making Selenium work for Facebook
41mWriting Well-Abstracted Self-Testing Automation On Top Of Jello-O
42mReliable and Maintainable Webdriver Tests
34mEnd to end testing a world of web, mobile & desktop apps
01h 14mContinuous Testing
30mEnd to End Testing: The Game Has Changed
19mWorking Well: The Future of Web Testing
31mEnd to end testing a world of web, mobile & desktop apps