Locator strategy
Explain how you choose stable CSS selectors, XPath expressions, test IDs, and text locators when the UI changes often.
- When would you avoid absolute XPath?
- How do you make a locator resilient?
- What makes a selector flaky in CI?
Prepare practical answers for Selenium WebDriver interviews, from locator strategy and waits to framework design, debugging, and CI reliability.
Explain how you choose stable CSS selectors, XPath expressions, test IDs, and text locators when the UI changes often.
Show that you understand explicit waits, page readiness, network timing, dynamic elements, and race conditions.
Describe page objects, reusable helpers, test data setup, assertions, reports, screenshots, and parallel execution.
Walk through how you triage failures from logs, screenshots, browser console errors, API traces, and environment differences.
Yes. The page covers beginner-friendly Selenium interview areas such as locators, waits, browser handling, assertions, and basic framework structure.
Practice writing stable locators, explaining waits, automating common form flows, debugging failed tests, and describing how automation fits into smoke and regression testing.
Selenium is still common in many QA jobs, while Playwright is growing fast for modern browser automation. Learning both helps you compare tools clearly in interviews.