Building Tests to Build Websites
summary
Claims a concrete mapping of a multi-frame Salesforce Communities platform onto the Page Object Model, shows client-side hooks and the actual code used to support that pattern, and walks through a live Selenium WebDriver example that sets up data before session start. Demonstrates using JavaScript executors to wait for web‑service completion, argues for API‑first tests and atomic cases, and reports real cross‑browser pain (including Internet Explorer). Useful if wanting working recipes and code tradeoffs rather than platitudes.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:39Outline
- 2:30Motivation
- 3:50Main Testing Concept
- 5:18Design Time
- 7:49Runtime
- 13:26Browsers
- 17:15Best Practices
- 22:02Code Reviews
- 25:00JavaScript Executor
- 27:22Why WebDriver
- 29:50Why Unit Tests
- 31:15Summary
- 34:08EndtoEnd Testing
- 35:35QA
- 37:08Working with the developer
- 40:35JavaScript Executors
- 43:04Avoid WebDriver
related talks
55mModern Web Testing: Going Beyond Selenium
36mModern Web Testing: Going Beyond Selenium
38mModern Web Testing: Going Beyond Selenium
30mModern Web Testing: Going Beyond Selenium
53mModern Web Testing: Going Beyond Selenium
57mPanel 7: Testing and tooling
19mWorking Well: The Future of Web Testing
41mFunctional Tests (Selenium) in Practice
