Why Does a Layout Designer Need Selenium
summary
Shows why frontend developers should use Selenium: install via npm install selenium-standalone, run Selenium as a local web server and control real browsers through the webdriver client, and prefer Selenium for integration/user-flow tests while keeping most checks as fast unit tests. Demonstrates capturing screenshots and generating Allure reports for step-by-step debugging, using the Page Object pattern for maintainable selectors, running tests on cloud/grid, and includes a ready example project with runnable tests.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:16Manual testing problems
- 3:44Unit testing for layout
- 7:17Integration tests with Selenium
- 10:05Setting up Selenium
- 13:15Debugging with screenshots
- 15:00Matchers in tests
- 17:12Page Object pattern
- 19:12Q&A
- 39:00Summary
related talks
32mHolistic cross browser testing with Selenium
36mModern Web Testing: Going Beyond Selenium
38mModern Web Testing: Going Beyond Selenium
55mModern Web Testing: Going Beyond Selenium
46mTest Automation with Selenium WebDriver, Java, and JUnit
36m3 ways not to use Selenium
53mModern Web Testing: Going Beyond Selenium
28mFrontend Testing
