Locators

CSS Locator in Playwright

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

Definition and Brief Explanation

Definition: A CSS locator finds elements using CSS selector syntax.

Explanation: CSS locators are powerful but can become fragile if they depend on generated classes, deep DOM paths, or layout structure. Use them when semantic locators cannot express the target clearly.

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: CSS attribute selector

await page.locator('input[name="email"]').fill('qa@example.com');

Explanation: Uses a stable HTML attribute instead of a long DOM path.

Example 2: Component selector

await page.locator('.product-card').first().click();

Explanation: Can work for stable classes, but generated CSS class names are risky.

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 CSS Locator in Playwright?
  2. When would you choose CSS 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 CSS Locator. Add one positive assertion, one note about what can go wrong, and one improvement that would make the test more maintainable.

☰