Dmitry Gozman
GitHub
parent
8c416653f9
commit
be150796f4
|
|
@ -67,65 +67,6 @@ await locator.HoverAsync();
|
|||
await locator.ClickAsync();
|
||||
```
|
||||
|
||||
## Creating Locators
|
||||
|
||||
Use [`method: Page.locator`] method to create a locator. This method takes a selector that describes how to find an element in the page. Playwright supports many different selectors like [Text](./selectors.md#text-selector), [CSS](./selectors.md#css-selector), [XPath](./selectors.md#xpath-selectors) and many more. Learn more about available selectors and how to pick one in this [in-depth guide](./selectors.md).
|
||||
|
||||
```js
|
||||
// Find by text.
|
||||
await page.locator('text=Sign up').click();
|
||||
|
||||
// Find by CSS.
|
||||
await page.locator('button.sign-up').click();
|
||||
|
||||
// Find by test id.
|
||||
await page.locator('data-testid=sign-up').click();
|
||||
```
|
||||
|
||||
```python async
|
||||
# Find by text.
|
||||
await page.locator("text=Sign up").click()
|
||||
|
||||
# Find by CSS.
|
||||
await page.locator("button.sign-up").click()
|
||||
|
||||
# Find by test id.
|
||||
await page.locator("data-testid=sign-up").click()
|
||||
```
|
||||
|
||||
```python sync
|
||||
# Find by text.
|
||||
page.locator("text=Sign up").click()
|
||||
|
||||
# Find by CSS.
|
||||
page.locator("button.sign-up").click()
|
||||
|
||||
# Find by test id.
|
||||
page.locator("data-testid=sign-up").click()
|
||||
```
|
||||
|
||||
```java
|
||||
// Find by text.
|
||||
page.locator("text=Sign up").click();
|
||||
|
||||
// Find by CSS.
|
||||
page.locator("button.sign-up").click();
|
||||
|
||||
// Find by test id.
|
||||
page.locator("data-testid=sign-up").click();
|
||||
```
|
||||
|
||||
```csharp
|
||||
// Find by text.
|
||||
await page.Locator("text=Sign up").ClickAsync();
|
||||
|
||||
// Find by CSS.
|
||||
await page.Locator("button.sign-up").ClickAsync();
|
||||
|
||||
// Find by test id.
|
||||
await page.Locator("data-testid=sign-up").ClickAsync();
|
||||
```
|
||||
|
||||
## Strictness
|
||||
|
||||
Locators are strict. This means that all operations on locators that imply
|
||||
|
|
@ -188,121 +129,321 @@ await page.Locator("button").CountAsync();
|
|||
```
|
||||
|
||||
:::caution
|
||||
Using [`method: Locator.first`], [`method: Locator.last`], and [`method: Locator.nth`] is discouraged since it disables the concept of strictness, and as your page changes, Playwright may click on an element you did not intend. It's better to make your locator more specific. Learn more below in [Filtering Locators](#filtering-locators) and the [selectors guide](./selectors.md).
|
||||
Using [`method: Locator.first`], [`method: Locator.last`], and [`method: Locator.nth`] is discouraged since it disables the concept of strictness, and as your page changes, Playwright may click on an element you did not intend. It's better to make your locator more specific.
|
||||
:::
|
||||
|
||||
## Lists
|
||||
|
||||
You can also use locators to work with the element lists.
|
||||
## Locating elements
|
||||
|
||||
Use [`method: Page.locator`] method to create a locator. This method takes a selector that describes how to find an element in the page. The choice of selectors determines the resiliency of the test when the underlying web page changes. To reduce the maintenance burden, we recommend prioritizing user-facing attributes and explicit contracts.
|
||||
|
||||
### Locate by text content using `text=`
|
||||
|
||||
The easiest way to find an element is to look for the text it contains.
|
||||
|
||||
```js
|
||||
// Locate elements, this locator points to a list.
|
||||
const rows = page.locator('table tr');
|
||||
await page.locator('text=Log in').click();
|
||||
```
|
||||
```java
|
||||
page.locator("text=Log in").click();
|
||||
```
|
||||
```python async
|
||||
await page.locator("text=Log in").click()
|
||||
```
|
||||
```python sync
|
||||
page.locator("text=Log in").click()
|
||||
```
|
||||
```csharp
|
||||
await page.Locator("text=Log in").ClickAsync();
|
||||
```
|
||||
|
||||
// Pattern 1: use locator methods to calculate text on the whole list.
|
||||
const texts = await rows.allTextContents();
|
||||
You can also [filter by text](#filter-by-text) when locating in some other way, for example find a particular item in the list.
|
||||
|
||||
// Pattern 2: do something with each element in the list.
|
||||
const count = await rows.count()
|
||||
for (let i = 0; i < count; ++i)
|
||||
console.log(await rows.nth(i).textContent());
|
||||
```js
|
||||
await page.locator('data-test-id=product-item', { hasText: 'Playwright Book' }).click();
|
||||
```
|
||||
```java
|
||||
page.locator("data-test-id=product-item", new Page.LocatorOptions().setHasText("Playwright Book")).click();
|
||||
```
|
||||
```python async
|
||||
await page.locator("data-test-id=product-item", has_text="Playwright Book").click()
|
||||
```
|
||||
```python sync
|
||||
page.locator("data-test-id=product-item", has_text="Playwright Book").click()
|
||||
```
|
||||
```csharp
|
||||
await page.Locator("data-test-id=product-item", new() { HasText = "Playwright Book" }).ClickAsync();
|
||||
```
|
||||
|
||||
// Pattern 3: resolve locator to elements on page and map them to their text content.
|
||||
// Note: the code inside evaluateAll runs in page, you can call any DOM apis there.
|
||||
const texts = await rows.evaluateAll(list => list.map(element => element.textContent));
|
||||
[Learn more about the `text` selector](./selectors.md#text-selector).
|
||||
|
||||
### Locate based on accessible attributes using `role=`
|
||||
|
||||
The `role` selector reflects how users and assistive technology percieve the page, for example whether some element is a button or a checkbox. When locating by role, you should usually pass the accessible name as well, so that locator pinpoints the exact element.
|
||||
|
||||
```js
|
||||
await page.locator('role=button[name=/submit/i]').click();
|
||||
|
||||
await page.locator('role=checkbox[checked][name="Check me"]').check();
|
||||
```
|
||||
|
||||
```python async
|
||||
# Locate elements, this locator points to a list.
|
||||
rows = page.locator("table tr")
|
||||
await page.locator('role=button[name=/submit/i]').click()
|
||||
|
||||
# Pattern 1: use locator methods to calculate text on the whole list.
|
||||
texts = await rows.all_text_contents()
|
||||
|
||||
# Pattern 2: do something with each element in the list.
|
||||
count = await rows.count()
|
||||
for i in range(count):
|
||||
print(await rows.nth(i).text_content())
|
||||
|
||||
# Pattern 3: resolve locator to elements on page and map them to their text content.
|
||||
# Note: the code inside evaluateAll runs in page, you can call any DOM apis there.
|
||||
texts = await rows.evaluate_all("list => list.map(element => element.textContent)")
|
||||
await page.locator('role=checkbox[checked][name="Check me"]').check()
|
||||
```
|
||||
|
||||
```python sync
|
||||
# Locate elements, this locator points to a list.
|
||||
rows = page.locator("table tr")
|
||||
page.locator('role=button[name=/submit/i]').click()
|
||||
|
||||
# Pattern 1: use locator methods to calculate text on the whole list.
|
||||
texts = rows.all_text_contents()
|
||||
|
||||
# Pattern 2: do something with each element in the list.
|
||||
count = rows.count()
|
||||
for i in range(count):
|
||||
print(rows.nth(i).text_content())
|
||||
|
||||
# Pattern 3: resolve locator to elements on page and map them to their text content.
|
||||
# Note: the code inside evaluateAll runs in page, you can call any DOM apis there.
|
||||
texts = rows.evaluate_all("list => list.map(element => element.textContent)")
|
||||
page.locator('role=checkbox[checked][name="Check me"]').check()
|
||||
```
|
||||
|
||||
```java
|
||||
// Locate elements, this locator points to a list.
|
||||
Locator rows = page.locator("table tr");
|
||||
page.locator("role=button[name=/submit/i]").click();
|
||||
|
||||
// Pattern 1: use locator methods to calculate text on the whole list.
|
||||
List<String> texts = rows.allTextContents();
|
||||
|
||||
// Pattern 2: do something with each element in the list.
|
||||
int count = rows.count()
|
||||
for (int i = 0; i < count; ++i)
|
||||
System.out.println(rows.nth(i).textContent());
|
||||
|
||||
// Pattern 3: resolve locator to elements on page and map them to their text content.
|
||||
// Note: the code inside evaluateAll runs in page, you can call any DOM apis there.
|
||||
Object texts = rows.evaluateAll("list => list.map(element => element.textContent)");
|
||||
page.locator("role=checkbox[checked][name=\"Check me\"]").check();
|
||||
```
|
||||
|
||||
```csharp
|
||||
// Locate elements, this locator points to a list.
|
||||
var rows = page.Locator("table tr");
|
||||
await page.Locator("role=button[name=/submit/i]").ClickAsync();
|
||||
|
||||
// Pattern 1: use locator methods to calculate text on the whole list.
|
||||
var texts = await rows.AllTextContentsAsync();
|
||||
|
||||
// Pattern 2: do something with each element in the list:
|
||||
var count = await rows.CountAsync()
|
||||
for (let i = 0; i < count; ++i)
|
||||
Console.WriteLine(await rows.Nth(i).TextContentAsync());
|
||||
|
||||
// Pattern 3: resolve locator to elements on page and map them to their text content
|
||||
// Note: the code inside evaluateAll runs in page, you can call any DOM apis there
|
||||
var texts = await rows.EvaluateAllAsync("list => list.map(element => element.textContent)");
|
||||
await page.Locator("role=checkbox[checked][name=\"Check me\"]").CheckAsync();
|
||||
```
|
||||
|
||||
## Filtering Locators
|
||||
[Learn more about the `role` selector](./selectors.md#role-selector).
|
||||
|
||||
When creating a locator, you can pass additional options to filter it.
|
||||
### Define explicit contract and use `data-test-id=`
|
||||
|
||||
Filtering by text will search for a particular string somewhere inside the element, possibly in a descendant element, case-insensitively. You can also pass a regular expression.
|
||||
User-facing attributes like text or accessible name can change frequently. In this case it is convenient to define explicit test ids, for example with a `data-test-id` attribute. Playwright has dedicated support for `id`, `data-test-id`, `data-test` and `data-testid` attributes.
|
||||
|
||||
```html
|
||||
<button data-test-id="directions">Itinéraire</button>
|
||||
```
|
||||
|
||||
```js
|
||||
await page.locator('button', { hasText: 'Sign up' }).click();
|
||||
```
|
||||
```java
|
||||
page.locator("button", new Page.LocatorOptions().setHasText("Sign up")).click();
|
||||
```
|
||||
```python async
|
||||
await page.locator("button", has_text="Sign up").click()
|
||||
```
|
||||
```python sync
|
||||
page.locator("button", has_text="Sign up").click()
|
||||
```
|
||||
```csharp
|
||||
await page.Locator("button", new PageLocatorOptions { HasText = "Sign up" }).ClickAsync();
|
||||
await page.locator('data-test-id=directions').click();
|
||||
```
|
||||
|
||||
Locators also support an option to only select elements that have a descendant matching another locator. Note that inner locator is matched starting from the outer one, not from the document root.
|
||||
```java
|
||||
page.locator("data-test-id=directions").click();
|
||||
```
|
||||
|
||||
```python async
|
||||
await page.locator('data-test-id=directions').click()
|
||||
```
|
||||
|
||||
```python sync
|
||||
page.locator('data-test-id=directions').click()
|
||||
```
|
||||
|
||||
```csharp
|
||||
await page.Locator("data-test-id=directions").ClickAsync();
|
||||
```
|
||||
|
||||
### Locate by label text
|
||||
|
||||
Most form controls usually have dedicated labels that could be conveniently used to interact with the form. Input actions in Playwright automatically distinguish between labels and controls, so you can just locate the label to perform an action on the associated control.
|
||||
|
||||
For example, consider the following DOM structure.
|
||||
|
||||
```html
|
||||
<label for="password">Password:</label><input type="password">
|
||||
```
|
||||
|
||||
You can target the label with something like `text=Password` and perform the following actions on the password input:
|
||||
- `click` will click the label and automatically focus the input field;
|
||||
- `fill` will fill the input field;
|
||||
- `inputValue` will return the value of the input field;
|
||||
- `selectText` will select text in the input field;
|
||||
- `setInputFiles` will set files for the input field with `type=file`;
|
||||
- `selectOption` will select an option from the select box.
|
||||
|
||||
For example, to fill the input by targeting the label:
|
||||
|
||||
```js
|
||||
await page.locator('text=Password').fill('secret');
|
||||
```
|
||||
|
||||
```java
|
||||
page.locator("text=Password").fill("secret");
|
||||
```
|
||||
|
||||
```python async
|
||||
await page.locator('text=Password').fill('secret')
|
||||
```
|
||||
|
||||
```python sync
|
||||
page.locator('text=Password').fill('secret')
|
||||
```
|
||||
|
||||
```csharp
|
||||
await page.Locator("text=Password").FillAsync("secret");
|
||||
```
|
||||
|
||||
However, other methods will target the label itself, for example `textContent` will return the text content of the label, not the input field.
|
||||
|
||||
### Locate in a subtree
|
||||
|
||||
You can chain [`method: Page.locator`] and [`method: Locator.locator`] calls to narrow down the search to a particular part of the page.
|
||||
|
||||
For example, consider the following DOM structure:
|
||||
|
||||
```html
|
||||
<div data-test-id='product-card'>
|
||||
<span>Product 1</span>
|
||||
<button>Buy</button>
|
||||
</div>
|
||||
<div data-test-id='product-card'>
|
||||
<span>Product 2</span>
|
||||
<button>Buy</button>
|
||||
</div>
|
||||
```
|
||||
|
||||
For example, we can first find a product card that contains text "Product 2", and then click the button in this specific product card.
|
||||
|
||||
```js
|
||||
const product = page.locator('data-test-id=product-card', { hasText: 'Product 2' });
|
||||
|
||||
await product.locator('text=Buy').click();
|
||||
```
|
||||
|
||||
```python async
|
||||
product = page.locator("data-test-id=product-card", has_text="Product 2")
|
||||
|
||||
await product.locator("text=Buy").click()
|
||||
```
|
||||
|
||||
```python sync
|
||||
product = page.locator("data-test-id=product-card", has_text="Product 2")
|
||||
|
||||
product.locator("text=Buy").click()
|
||||
```
|
||||
|
||||
```java
|
||||
Locator product = page.locator("data-test-id=product-card", new Page.LocatorOptions().setHasText("Product 2"));
|
||||
|
||||
product.locator("text=Buy").click();
|
||||
```
|
||||
|
||||
```csharp
|
||||
var product = page.Locator("data-test-id=product-card", new() { HasText = "Product 2" });
|
||||
|
||||
await product.Locator("text=Buy").clickAsync();
|
||||
```
|
||||
|
||||
### Locate by CSS or XPath selector
|
||||
|
||||
Playwright supports CSS and XPath selectors, and auto-detects them if you omit `css=` or `xpath=` prefix:
|
||||
|
||||
```js
|
||||
await page.locator('css=button').click();
|
||||
await page.locator('xpath=//button').click();
|
||||
|
||||
await page.locator('button').click();
|
||||
await page.locator('//button').click();
|
||||
```
|
||||
|
||||
```java
|
||||
page.locator("css=button").click();
|
||||
page.locator("xpath=//button").click();
|
||||
|
||||
page.locator("button").click();
|
||||
page.locator("//button").click();
|
||||
```
|
||||
|
||||
```python async
|
||||
await page.locator('css=button').click()
|
||||
await page.locator('xpath=//button').click()
|
||||
|
||||
await page.locator('button').click()
|
||||
await page.locator('//button').click()
|
||||
```
|
||||
|
||||
```python sync
|
||||
page.locator('css=button').click()
|
||||
page.locator('xpath=//button').click()
|
||||
|
||||
page.locator('button').click()
|
||||
page.locator('//button').click()
|
||||
```
|
||||
|
||||
```csharp
|
||||
await page.Locator('css=button').ClickAsync();
|
||||
await page.Locator('xpath=//button').ClickAsync();
|
||||
|
||||
await page.Locator('button').ClickAsync();
|
||||
await page.Locator('//button').ClickAsync();
|
||||
```
|
||||
|
||||
### Avoid locators tied to implementation
|
||||
|
||||
XPath and CSS selectors can be tied to the DOM structure or implementation. These selectors can break when the DOM structure changes. Similarly, [`method: Locator.nth`], [`method: Locator.first`], and [`method: Locator.last`] are tied to implementation and the structure of the DOM, and will target the incorrect element if the DOM changes.
|
||||
|
||||
Long CSS or XPath chains below are an example of a **bad practice** that leads to unstable tests:
|
||||
|
||||
```js
|
||||
await page.locator('#tsf > div:nth-child(2) > div.A8SBwf > div.RNNXgb > div > div.a4bIc > input').click();
|
||||
|
||||
await page.locator('//*[@id="tsf"]/div[2]/div[1]/div[1]/div/div[2]/input').click();
|
||||
```
|
||||
|
||||
```java
|
||||
page.locator("#tsf > div:nth-child(2) > div.A8SBwf > div.RNNXgb > div > div.a4bIc > input").click();
|
||||
|
||||
page.locator("//*[@id='tsf']/div[2]/div[1]/div[1]/div/div[2]/input").click();
|
||||
```
|
||||
|
||||
```python async
|
||||
await page.locator('#tsf > div:nth-child(2) > div.A8SBwf > div.RNNXgb > div > div.a4bIc > input').click()
|
||||
|
||||
await page.locator('//*[@id="tsf"]/div[2]/div[1]/div[1]/div/div[2]/input').click()
|
||||
```
|
||||
|
||||
```python sync
|
||||
page.locator('#tsf > div:nth-child(2) > div.A8SBwf > div.RNNXgb > div > div.a4bIc > input').click()
|
||||
|
||||
page.locator('//*[@id="tsf"]/div[2]/div[1]/div[1]/div/div[2]/input').click()
|
||||
```
|
||||
|
||||
```csharp
|
||||
await page.Locator("#tsf > div:nth-child(2) > div.A8SBwf > div.RNNXgb > div > div.a4bIc > input").ClickAsync();
|
||||
|
||||
await page.Locator("//*[@id='tsf']/div[2]/div[1]/div[1]/div/div[2]/input").ClickAsync();
|
||||
```
|
||||
|
||||
Instead, try to come up with a locator that is close to how user perceives the page or [define an explicit testing contract](#define-explicit-contract-and-use-data-test-id).
|
||||
|
||||
### Locate elements that contain other elements
|
||||
|
||||
#### Filter by text
|
||||
|
||||
Locator can be optionally filtered by text. It will search for a particular string somewhere inside the element, possibly in a descendant element, case-insensitively. You can also pass a regular expression.
|
||||
|
||||
```js
|
||||
await page.locator('button', { hasText: 'Click me' }).click();
|
||||
await page.locator('button', { hasText: /Click me/ }).click();
|
||||
```
|
||||
```java
|
||||
page.locator("button", new Page.LocatorOptions().setHasText("Click me")).click();
|
||||
page.locator("button", new Page.LocatorOptions().setHasText(Pattern.compile("Click me"))).click();
|
||||
```
|
||||
```python async
|
||||
await page.locator("button", has_text="Click me").click()
|
||||
await page.locator("button", has_text=re.compile("Click me")).click()
|
||||
```
|
||||
```python sync
|
||||
page.locator("button", has_text="Click me").click()
|
||||
page.locator("button", has_text=re.compile("Click me")).click()
|
||||
```
|
||||
```csharp
|
||||
await page.Locator("button", new() { HasText = "Click me" }).ClickAsync();
|
||||
await page.Locator("button", new() { HasText = new Regex("Click me") }).ClickAsync();
|
||||
```
|
||||
|
||||
#### Filter by another locator
|
||||
|
||||
Locators support an option to only select elements that have a descendant matching another locator.
|
||||
|
||||
```js
|
||||
page.locator('article', { has: page.locator('button.subscribe') })
|
||||
|
|
@ -317,10 +458,14 @@ page.locator("article", has=page.locator("button.subscribe"))
|
|||
page.locator("article", has=page.locator("button.subscribe"))
|
||||
```
|
||||
```csharp
|
||||
page.Locator("article", new PageLocatorOptions { Has = page.Locator("button.subscribe") })
|
||||
page.Locator("article", new() { Has = page.Locator("button.subscribe") })
|
||||
```
|
||||
|
||||
You can also filter an existing locator with [`method: Locator.filter`] method, possibly chaining it multiple times.
|
||||
Note that inner locator is matched starting from the outer one, not from the document root.
|
||||
|
||||
#### Augment an existing locator
|
||||
|
||||
You can filter an existing locator by text or another one, using [`method: Locator.filter`] method, possibly chaining it multiple times.
|
||||
|
||||
```js
|
||||
const rowLocator = page.locator('tr');
|
||||
|
|
@ -367,6 +512,185 @@ await rowLocator
|
|||
.ScreenshotAsync();
|
||||
```
|
||||
|
||||
### Locate elements in Shadow DOM
|
||||
|
||||
All locators in Playwright **by default** work with elements in Shadow DOM. The exceptions are:
|
||||
- Locating by XPath selector does not pierce shadow roots.
|
||||
- [Closed-mode shadow roots](https://developer.mozilla.org/en-US/docs/Web/API/Element/attachShadow#parameters) are not supported.
|
||||
|
||||
Consider the following example with a custom web component:
|
||||
```html
|
||||
<x-badge>
|
||||
<span>Title</span>
|
||||
#shadow-root
|
||||
<span>Details</span>
|
||||
</x-badge>
|
||||
```
|
||||
|
||||
You can locate in the same way as if the shadow root was not present at all.
|
||||
|
||||
- Click `<span>Details</span>`
|
||||
```js
|
||||
await page.locator('text=Details').click();
|
||||
```
|
||||
```java
|
||||
page.locator("text=Details").click();
|
||||
```
|
||||
```python async
|
||||
await page.locator("text=Details").click()
|
||||
```
|
||||
```python sync
|
||||
page.locator("text=Details").click()
|
||||
```
|
||||
```csharp
|
||||
await page.Locator("text=Details").ClickAsync();
|
||||
```
|
||||
|
||||
- Click `<x-badge>`
|
||||
```js
|
||||
await page.locator('x-badge', { hasText: 'Details' }).click();
|
||||
```
|
||||
```java
|
||||
page.locator("x-badge", new Page.LocatorOptions().setHasText("Details")).click();
|
||||
```
|
||||
```python async
|
||||
await page.locator("x-badge", has_text="Details" ).click()
|
||||
```
|
||||
```python sync
|
||||
page.locator("x-badge", has_text="Details" ).click()
|
||||
```
|
||||
```csharp
|
||||
await page.Locator("x-badge", new() { HasText = "Details" }).ClickAsync();
|
||||
```
|
||||
|
||||
- Ensure that `<x-badge>` contains text "Details"
|
||||
```js
|
||||
await expect(page.locator('x-badge')).toContainText('Details');
|
||||
```
|
||||
```java
|
||||
assertThat(page.locator("x-badge")).containsText("Details");
|
||||
```
|
||||
```python async
|
||||
await expect(page.locator("x-badge")).to_contain_text("Details")
|
||||
```
|
||||
```python sync
|
||||
expect(page.locator("x-badge")).to_contain_text("Details")
|
||||
```
|
||||
```csharp
|
||||
await Expect(page.Locator("x-badge")).ToContainTextAsync("Details");
|
||||
```
|
||||
|
||||
## Lists
|
||||
|
||||
You can also use locators to work with the element lists.
|
||||
|
||||
For example, let's create a locator pointing to a list:
|
||||
|
||||
```js
|
||||
const rows = page.locator('table tr');
|
||||
```
|
||||
```python async
|
||||
rows = page.locator("table tr")
|
||||
```
|
||||
```python sync
|
||||
rows = page.locator("table tr")
|
||||
```
|
||||
```java
|
||||
Locator rows = page.locator("table tr");
|
||||
```
|
||||
```csharp
|
||||
var rows = page.Locator("table tr");
|
||||
```
|
||||
|
||||
- Pattern 1: use locator methods to calculate text on the whole list
|
||||
```js
|
||||
const texts = await rows.allTextContents();
|
||||
```
|
||||
```python async
|
||||
texts = await rows.all_text_contents()
|
||||
```
|
||||
```python sync
|
||||
texts = rows.all_text_contents()
|
||||
```
|
||||
```java
|
||||
List<String> texts = rows.allTextContents();
|
||||
```
|
||||
```csharp
|
||||
var texts = await rows.AllTextContentsAsync();
|
||||
```
|
||||
|
||||
- Pattern 2: do something with each element in the list
|
||||
```js
|
||||
const count = await rows.count()
|
||||
for (let i = 0; i < count; ++i)
|
||||
console.log(await rows.nth(i).textContent());
|
||||
```
|
||||
```python async
|
||||
count = await rows.count()
|
||||
for i in range(count):
|
||||
print(await rows.nth(i).text_content())
|
||||
```
|
||||
```python sync
|
||||
count = rows.count()
|
||||
for i in range(count):
|
||||
print(rows.nth(i).text_content())
|
||||
```
|
||||
```java
|
||||
int count = rows.count()
|
||||
for (int i = 0; i < count; ++i)
|
||||
System.out.println(rows.nth(i).textContent());
|
||||
```
|
||||
```csharp
|
||||
var count = await rows.CountAsync()
|
||||
for (let i = 0; i < count; ++i)
|
||||
Console.WriteLine(await rows.Nth(i).TextContentAsync());
|
||||
```
|
||||
|
||||
- Pattern 3: resolve locator to elements on page and map them to their text content. Note that code inside [`method: Locator.evaluateAll`] runs in the web page and you can call any DOM apis there.
|
||||
```js
|
||||
const texts = await rows.evaluateAll(list => list.map(element => element.textContent));
|
||||
```
|
||||
```python async
|
||||
texts = await rows.evaluate_all("list => list.map(element => element.textContent)")
|
||||
```
|
||||
```python sync
|
||||
texts = rows.evaluate_all("list => list.map(element => element.textContent)")
|
||||
```
|
||||
```java
|
||||
Object texts = rows.evaluateAll("list => list.map(element => element.textContent)");
|
||||
```
|
||||
```csharp
|
||||
var texts = await rows.EvaluateAllAsync("list => list.map(element => element.textContent)");
|
||||
```
|
||||
|
||||
### Picking specific element from a list
|
||||
|
||||
If you have a list of identical elements, and the only way to distinguish between them is the order, you can choose a specific element from a list with [`method: Locator.first`], [`method: Locator.last`] or [`method: Locator.nth`].
|
||||
|
||||
However, use these methods with caution. Often times, the page might change, and locator will point to a completely different element from the one you expected. Instead, try to come up with a unique locator that will pass the [strictness criteria](#strictness).
|
||||
|
||||
For example, to click the third item in the list of products:
|
||||
|
||||
```js
|
||||
await page.locator('data-test-id=product-card').nth(3).click();
|
||||
```
|
||||
|
||||
```java
|
||||
page.locator("data-test-id=product-card").nth(3).click();
|
||||
```
|
||||
|
||||
```python async
|
||||
await page.locator("data-test-id=product-card").nth(3).click()
|
||||
```
|
||||
|
||||
```python sync
|
||||
page.locator("data-test-id=product-card").nth(3).click()
|
||||
```
|
||||
|
||||
```csharp
|
||||
await page.Locator("data-test-id=product-card").Nth(3).ClickAsync();
|
||||
```
|
||||
|
||||
## Locator vs ElementHandle
|
||||
|
||||
:::caution
|
||||
|
|
|
|||
Loading…
Reference in a new issue