UI Automation for Quality Assurance (QA)s
UI automation is the use of code to drive a browser the way a user does and assert on what appears. Playwright, Selenium and Cypress are the main tools, and page objects and similar design patterns keep the scripts readable and cheap to maintain as the interface changes.
Stage: Test Automation · Part of the Quality Assurance (QA) roadmap · Last reviewed 19 November 2026
What to learn in UI Automation
- Write a Playwright test that logs in and checks a result
- Choose locators by role or test id rather than fragile XPath
- Use auto-waiting and explicit waits instead of fixed sleeps
- Compare Playwright, Selenium and Cypress by architecture and trade-offs
- Wrap a page in a page object class with intent-named methods
- Share setup through fixtures instead of repeating steps
UI Automation interview questions
What is the page object model and why use it?
It is a pattern where each page or component gets a class holding its locators and actions. Tests call methods like login rather than touching selectors. When the UI changes, you update one class instead of every test.
Why are fixed sleeps a bad way to wait in UI tests?
A fixed sleep either wastes time when the page is ready early or fails when it is slow. Waiting on a condition, such as an element being visible or a network response arriving, is both faster and more reliable.
Where UI Automation fits in the Quality Assurance (QA) roadmap
UI Automation belongs to the Test Automation stage (beginner level), which takes about 9 hours. Reliable, maintainable checks.
Other units in this stage
Back to the full Quality Assurance (QA) roadmap