Locators
Title Locator in Playwright
Title Locator in Playwright: definition, detailed explanation, practical usage, examples, mistakes, interview notes, and practice for Playwright automation.
Definition and Brief Explanation
Definition: A title locator finds an element by its title attribute.
Explanation: Title locators are useful for elements that expose extra tooltip-like text through the title attribute. They should not be the default choice because title attributes are often inconsistent and not always visible to users.
Why It Matters
- It makes tests easier to read because the locator describes the target element clearly.
- It reduces flaky failures caused by layout changes or generated CSS classes.
- It works with Playwright auto-waiting, so actions and assertions wait for the element state.
- It supports maintainable Page Object Model code because selectors are meaningful.
How It Works
- Identify the element by user-facing meaning first: role, label, text, placeholder, alt text, or title.
- Confirm the locator points to the intended element and is unique when used for an action.
- Use filters, chaining, or test ids when the page has repeated controls.
- Avoid positional locators unless order is the behavior being tested.
Syntax and Examples
Example 1: Title attribute
await page.getByTitle('Close').click();
Explanation: Useful for icon-only controls that expose a title attribute.
Common Mistakes
- Using generated CSS classes as the first option.
- Using broad text that appears in many places.
- Adding nth() only to silence strict mode.
- Storing element handles instead of using locators.
Interview Notes
- What is a Title Locator in Playwright?
- When would you choose Title Locator?
- How do you make the locator unique?
- What makes this locator stable or unstable?
Practice Task
Create a small Playwright example for Title Locator. Add one positive assertion, one note about what can go wrong, and one improvement that would make the test more maintainable.