Locators

Placeholder Locator in Playwright

Placeholder Locator in Playwright: definition, detailed explanation, practical usage, examples, mistakes, interview notes, and practice for Playwright automation.

Definition and Brief Explanation

Definition: A placeholder locator finds an input by its placeholder text.

Explanation: Placeholder locators are useful when a field has no visible label but shows guidance inside the input. They are less ideal than label locators because placeholder text can disappear after typing and may change for UX reasons.

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

  1. Identify the element by user-facing meaning first: role, label, text, placeholder, alt text, or title.
  2. Confirm the locator points to the intended element and is unique when used for an action.
  3. Use filters, chaining, or test ids when the page has repeated controls.
  4. Avoid positional locators unless order is the behavior being tested.

Syntax and Examples

Example 1: Search placeholder

await page.getByPlaceholder('Search lessons').fill('Playwright locators');

Explanation: Targets an input using placeholder text. Use it when the placeholder is stable and meaningful.

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

  1. What is a Placeholder Locator in Playwright?
  2. When would you choose Placeholder Locator?
  3. How do you make the locator unique?
  4. What makes this locator stable or unstable?

Practice Task

Create a small Playwright example for Placeholder Locator. Add one positive assertion, one note about what can go wrong, and one improvement that would make the test more maintainable.

☰