Locators

Locator Chaining in Playwright

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

Definition and Brief Explanation

Definition: Locator chaining creates a locator inside another locator.

Explanation: Chaining keeps the search scoped to a parent area such as a dialog, row, card, or navigation menu. It makes tests safer when the same button or text appears in multiple places.

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: Row then button

const row = page.getByRole('row', { name: /qa@example.com/ });
await row.getByRole('button', { name: 'Delete' }).click();

Explanation: Searches for Delete only inside the matching row, preventing wrong-row clicks.

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 does Locator Chaining mean in Playwright?
  2. When would you choose Locator Chaining?
  3. How do you make the locator unique?
  4. What makes this locator stable or unstable?

Practice Task

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

☰