Testing and moving fast making Selenium work for Facebook
summary
Facebook runs pre-review tests via Fabricator and sassle that aim for a 10 minute target for initial feedback, uses PHP WebDriver bindings (open sourced) that speak the JSON Wire Protocol, and enforces a workflow where failing or flaky tests are auto-assigned to the committer and deleted after 24 hours if not fixed. Web uses weekly trunk releases; mobile moved to native with four‑week release cycles. Pages include a test ID attribute contract for stable element selection and Peaceable provides VNC-hosted app previews.
AI-written summary · about
chapters (13)
- 0:00Intro
- 9:08Speed
- 9:43Signal
- 10:59Writing tests
- 13:41New bindings
- 14:53Test integration
- 16:58Mobile first
- 21:06UI testing for mobile
- 22:54Testing across apps
- 26:04Release cycle
- 28:56Test ID attribute
- 30:31Mobile infrastructure
- 31:40Webdriver bindings
related talks
23mReadable. Stable. Maintainable. E2E Testing @ Facebook
41mWriting Well-Abstracted Self-Testing Automation On Top Of Jello-O
01h 14mContinuous Testing
37mSelenium In the Enterprise: What went right, what went wrong (so far)
39mHow I learned testing from mobile browsers
21mThe Web has evolved. Has your testing evolved too?
29mState of Web Integration Testing
45mTesting the web without testers — success or failure