In this example we first create a locator called product by locating its role of listitem. We then filter by text.

Resolves given locator to all matching DOM elements. If there are no matching elements, returns an empty list.

A locator can be created with the page.locator() method. Learn more about locators. ... When the locator points to a list of elements, this returns an array of locators, pointing to their respective elements.

Resolves given locator to all matching DOM elements. If there are no matching elements, returns an empty list.

November 7, 2025 - Additionally, Playwright excels at locating input elements in web forms, such as those with placeholder text, making it easier to automate interactions like logging in or submitting reviews. Playwright supports multiple strategies for selecting elements, including: CSS Selectors: For selecting elements based on their CSS properties. ... XPath: For selecting elements with XPath expressions. const listItem = page.locator(‘//ul/li\[3\]’);

January 13, 2026 - On the filtered list_heading_locator, we call the except() assertion and ensure we have only located the exact list item (for input form submission) that we intended to locate. ... It’s not always possible for a single locator to locate the exact element on a web page. In such scenarios, chaining is the second method to narrow the search to a specific element by combining multiple Playwright locators.

When the locator points to a list of elements, returns a list of locators, each addressing their respective elements. Playwright.Locator.all/1 does not wait for elements to match the locator, and instead immediately returns whatever is present in the page. When the list of elements changes ...

February 2, 2026 - Today, we will delve into Playwright locators in more detail, and you can find all the information about them in the relevant section of the documentation on the official site playwright.dev. Here, you’ll explore a list of built-in locators, including their usage.

This provides a stable way to locate less likely to change elements. ... Class names can be used when IDs or accessibility IDs are not available. However, they may not be unique and can change if the UI is updated. ... Non-Unique: Multiple elements may share the same class. Maintenance: Changes in styles can affect selectors. ... Playwright supports native locator strategies interpreted by the underlying automation frameworks, such as -android uiautomator, -ios predicate string, and -ios class chain.

A string containing expected class names, separated by spaces, or a list of such strings to assert multiple elements. ... Time to retry the assertion for in milliseconds. Defaults to timeout in TestConfig.expect. ... Ensures the Locator points to an element that contains the given text.

Note that resulting matches are sorted by their distance to the anchor element, so you can use locator.first() to pick the closest one. This is only useful if you have something like a list of similar elements, where the closest is obviously the right one.

Resolves given locator to all matching DOM elements. If there are no matching elements, returns an empty list.

There are many ways to get a specific item in a list. Use the page.get_by_text() method to locate an element in a list by its text content and then click on it.

Auto waiting means that Playwright performs a range of actionability checks on the elements, such as ensuring the element is visible and enabled before it performs the click. ... The HTML <a> element comes with the implicitly defined role of link, so we don't need to modify the HTML in order to get this role. ... That means we can locate an <a> element by using the getByRole() locator, with the role of link and add the click method to the end of it.

Resolves the given Playwright.Locator to the first matching DOM element. If no elements matching the query are visible, waits for them up to a given timeout. If multiple elements match the selector, throws. ... Resolves given locator to all matching DOM elements. ... Returns the result of executing param: expression. Passes the handle as the first argument to the expression. ... Finds all elements matching the specified locator and passes the list ...

Locators are the central piece of Playwright's auto-waiting and retry-ability. In a nutshell, locators represent a way to find element(s) on the page at any moment. A locator can be created with the [method: Page.locator] method.

Each text value from the expected array is matched by some element from the list. ... from playwright.sync_api import expect # ✓ Contains the right items in the right order expect(page.locator("ul > li")).to_contain_text(["Text 1", "Text 3"]) # ✖ Wrong order expect(page.locator("ul > li")).to_contain_text(["Text 3", "Text 2"]) # ✖ No item contains this text expect(page.locator("ul > li")).to_contain_text(["Some 33"]) # ✖ Locator points to the outer list element, not to the list items expect(page.locator("ul")).to_contain_text(["Text 3"])

December 1, 2021 - let arrayOfLocators = page.locator('element); for (let singleLocator of arrayOfLocators) { const textOfElement = await singleLocator.innerText(); }

July 30, 2024 - Chain locators one by one, searching a child element within the scope of the previous locator. ... This finds a button with the text "Submit" within an "app-form" element. Playwright includes a powerful built-in tool called the Locator Picker.

February 11, 2025 - In this blog post, we’ll dive deep into Playwright automation locators, their types, best practices for using them, and practical examples to enhance your automation strategy.