Protractor: The Hacker Way
summary
Explains why Protractor fails on obvious steps: linkText is case-sensitive so CSS text-transform breaks locators, fast webdriver clicks race CSS animations, and ng e2e is slow because it updates webdriver and serves each run. Shows concrete fixes: use ExpectedConditions instead of sleeps (example waiting up to 5s), set chromeOptions for fixed window size/position and headless, persist sessions with user-data-dir to skip logins, and demos a Chrome extension protractor-recorder plus a fedora proxy rule to strip navigator.webdriver — all demos run and pass.
AI-written summary · about
chapters (7)
- 0:00Introduction to Protractor
- 1:54Basic testing workflow
- 3:56Handling common test failures
- 8:18Solving animation sync issues
- 12:56Protractor recorder tool
- 18:20Advanced configuration
- 23:25Bypassing robot detection
related talks
42mProtractor Framework – Making Stable e2e Tests for Angular Applications
23mProtractor: A New Hope
37mEmbrace Innovation: Designing A Protractor Framework For Angular2 Applications
43mPuppeteer Is the New WebDriver? Secrets of Flawless Testing
36mModern Web Testing: Going Beyond Selenium
49mProtractor: creating your first script
30mBrowser Testing
28mFrontend Testing