Skip to main content

Page Element Query Language

Serenity/JS Page Element Query Language (PEQL) is a Screenplay Pattern-compatible abstraction layer offering a flexible, composable, and extensible way to identify web elements in even the most complex web interfaces.

PEQL is designed to help you create portable web automation code optimised for ease of comprehension, reuse, and reducing test maintenance costs across your organisation.

Serenity/JS Page Element Query Language uses 3 simple, composable abstractions based on Screenplay questions that help you identify and interact with web elements of interest:

  • PageElement - models a single web element,
  • PageElements - models a collection of web elements,
  • By - represents portable locators used by your browser to identify web elements of interest.

In this section, you'll learn how to use them together to find the exact elements your tests need to interact with.

Working with individual page elements​

To show you how to work with individual page elements, I'll use an example shopping basket widget and demonstrate locating its various parts. The widget is simple enough to help us focus on the important aspects of PEQL, yet sophisticated enough to be representative of other widgets you're likely to come across in the wild:

<div id="basket">
  <ul>
    <li class="item">
      <span class="name">apples</span>
      <span class="price">£2.25</span>
    </li>
    <li class="item">
      <span class="name">bananas</span>
      <span class="price">£1.50</span>
    </li>
  </ul>
  <div class="total">£3.75</div>
</div>

Identifying individual page elements​

One of the most common things to implement in a web-based test scenario is an interaction with a web element, like clicking on an button, entering a value into a form field, or asserting on some message presented to the end-user.

Of course, to interact with an element you need to tell your test how to find it. In Serenity/JS, you can define an individual page element like this:

import { By, PageElement } from '@serenity-js/web'

export const basketTotal = () =>                // <- Function representing a domain concept
  PageElement.located(By.css('#basket .total')) // <- The way to locate the element, e.g. a CSS selector
    .describedAs('basket total')                // <- Description for reporting purposes

To define a page element:

  • Create a function named after the domain concept represented by the UI widget, such as basketTotal.
  • Make the function return a PageElement, configured to locate the element using one of the built-in By selectors.
  • Give your page element a human-readable description to be used when reporting interactions with the element.
Writing portable test code

Note how giving your test functions meaningful names, such as basketTotal, helps to make your code easier to read and understand. Also note how using the PageElement and By APIs helps your code remain declarative, portable, and agnostic of low-level integration tool-specific method calls, further improving its reusability.

Retrieving attributes of a page element​

Serenity/JS favours functional composition to help your code achieve polymorphic behaviour and promote code reuse. In practice, this means that in order to retrieve a specific attribute of a PageElement, you compose the element with an appropriate web question.

For example, to retrieve the text value of a PageElement returned by Basket.total(), compose it with a question about its Text:

import { By, PageElement, Text } from '@serenity-js/web'

export const basketTotal = () =>
  PageElement.located(By.css('#basket .total'))
    .describedAs('basket total')

export const basketTotalAmount = () =>
  Text.of(basketTotal())                    // <- Compose PageElement with question about Text
    .describedAs('basket total price')      // <- Custom description (optional)

Serenity/JS web module offers several web-specific questions you can compose with PageElement, such as Attribute, CssClasses, Value, and others.

Using selector aliases​

In scenarios where elements use a consistent pattern allowing them to be easily identified, such as a data-test-it, or a role attribute, you might want to implement custom selector aliases to avoid code duplication.

For example, below function byRole helps to locate elements with a desired accessibility role:

import { actorCalled } from '@serenity-js/core'
import { By, Click, PageElement } from '@serenity-js/web'

const byRole = (roleName: string) =>
    By.css(`[role="${ roleName }"]`)

await actorCalled('Alice').attemptsTo(
    Click.on(PageElement.located(byRole('button'))),
)

Using dynamic selectors​

In some scenarios, the exact value of the selector you need to use becomes known only at runtime. This is typically the case when element attributes are calculated dynamically based on user actions.

To cater for that, all By selectors let you define selector value using an Answerable<string>:

import { Answerable, q } from '@serenity-js/core'
import { By, PageElement } from '@serenity-js/web'

const byTestId = (dataTestId: Answerable<string>) =>
    PageElement.located(By.css(q`[data-test-id="${ dataTestId }"]`))

Note that the example above uses tag function q to concatenate a static string with an Answerable<string>.

Transforming answers to questions​

Serenity/JS questions offer not just a way to retrieve information, but also a powerful adapter mechanism that gives you a consistent API to proxy the methods and fields of the underlying answer type, allowing you to transform the value before it's returned.

For example, Text.of(pageElement) returns a QuestionAdapter<string>, which proxies methods available on the string type, such as trim or replace. Additionally, Question.as API offers a way to transform the answer to a question to another type.

Those two mechanisms combined give you a unique and flexible way to retrieve and transform information about the system under test and get it in the exact format you need.

For example, instead of retrieving the basket total amount as string you might want to clean it up and transform into a number:

import { By, PageElement, Text } from '@serenity-js/web'

export const basketTotal = () =>
  PageElement.located(By.css('#basket .total'))
    .describedAs('basket total')

export const basketTotalAmount = () =>
  Text.of(basketTotal())                // <- Compose PageElement with question about Text
    .trim()                             // <-   Compose with a question that trims the result
    .replace('£', '')                   // <-   Compose with a question that removes the currency symbol
    .as(Number)                         // <-   Compose with a question that converts the result to Number
    .describedAs('basket total price')  // <- Custom description (optional)

Performing assertions​

Serenity/JS web module provides web-specific expectations you use to verify if the actual state of the given element is what you expect it to be.

For example, you might want to ensure that a given element is visible, i.e. not obstructed by other elements:

import { actorCalled } from '@serenity-js/core'
import { Ensure } from '@serenity-js/assertions'
import { isVisible } from '@serenity-js/web'

await actorCalled('Alice').attemptsTo(
  Ensure.that(basketTotal(), isVisible()),
)

You can also assert that a specific property of the element, like its text, has a certain value:

import { actorCalled } from '@serenity-js/core'
import { Ensure, equals } from '@serenity-js/assertions'
import { Text } from '@serenity-js/web'


await actorCalled('Alice').attemptsTo(
  Ensure.that(Text.of(basketTotal()), equals('£3.75')),
)

Note that Serenity/JS expectations are type-safe and portable. This means that you're not limited to using just the web-specific expectations in your web tests, and you can use any other expectations from the Serenity/JS assertions module or even write them yourself.

Learn more

Learn more about asserting on page elements in chapter "Web assertions".

Waiting for condition​

Serenity/JS web module provides web-specific expectations you use to synchronise your test code with the system under test and wait until its state meets your expectations.

For example, you might want for your test scenario to wait until a given element is present in the DOM tree:

import { actorCalled, Duration, Wait } from '@serenity-js/core'
import { isPresent } from '@serenity-js/web'

await actorCalled('Alice').attemptsTo(
  Wait.upTo(Duration.ofSeconds(2))
    .until(basketTotal(), isPresent()),
)

You can also wait for a specific property of the element, like its text, to have a certain value:

import { actorCalled, Wait } from '@serenity-js/core'
import { startsWith } from '@serenity-js/assertions'
import { Text } from '@serenity-js/web'

await actorCalled('Alice').attemptsTo(
  Wait.until(Text.of(basketTotal()), startsWith('£')),
)

Note that just like with performing the assertions, your web scenarios can use all the expectations from the Serenity/JS assertions module or you can write some them yourself.

Learn more

Learn more about synchronising your web tests with the system under test in chapter "Waiting and synchronisation".

Just-in-time evaluation of questions​

Serenity/JS questions, like the PageElement returned by calling basketTotal(), or a chain of composed questions like Text.of(basketTotal()).trim().replace('£', '').as(Number), represent a mechanism for the actor to retrieve the value, and not the value itself.

As such, questions are evaluated just-in-time and only when the actor needs to retrieve the underlying value.

For example, the text of the basket total is retrieved only when an actor performs an assertion:

import { actorCalled } from '@serenity-js/core'
import { Ensure, equals } from '@serenity-js/assertions'
import { Text } from '@serenity-js/web'

export const basketTotalAmount = () =>  //     
  Text.of(basketTotal())                // <- A question describes a way for an actor
    .describedAs('basket total price')  //    to retrieve some information

await actorCalled('Alice').attemptsTo(
  Ensure.that(                          // <- A task like `Ensure` makes the actor "answer"
    basketTotalAmount(),                //    the question and retrieve the value 
    equals('£3.75')
  )
)

This just-in-time evaluation mechanism also has another benefit. It allows Serenity/JS questions to be used in tool- and interface-agnostic synchronisation tasks, where it might take several attempts until the question returns the desired result:

import { actorCalled, Duration, Wait } from '@serenity-js/core'
import { equals } from '@serenity-js/assertions'
import { Text } from '@serenity-js/web'

await actorCalled('Alice').attemptsTo(
  Wait.until(basketTotalAmount(), equals('£3.75'))
    .pollingEvery(Duration.ofMilliseconds(500))
)
Pro Tip

Note that the result of composing questions is also a question. This design makes questions reusable and allows for them to be composed further, until they're finally resolved by an actor.

Working with a collection of page elements​

PageElements class is a Screenplay Pattern-compatible abstraction that represents a collection of elements in a web interface that share some common characteristic.

To help you understand how to use this abstraction, remember the shopping basket widget I showed you earlier:

<div id="basket">
  <ul>
    <li class="item">
      <span class="name">apples</span>
      <span class="price">£2.25</span>
    </li>
    <li class="item">
      <span class="name">bananas</span>
      <span class="price">£1.50</span>
    </li>
  </ul>
  <div class="total">£3.75</div>
</div>

Modelling a collection of page elements​

Similarly to how you model a single page element, to model a collection of page elements:

  • Create a function that captures the name of the concept they represent, like basketItems.
  • Make the function return a PageElements object.
  • Define a custom description to be used for reporting purposes.

For example, you could represent the items displayed in the shopping basket as follows:

import { By, PageElements } from '@serenity-js/web'

const basketItems = () =>
  PageElements.located(By.css('#basket .item')) // <- Note plural `PageElements` 
    .describedAs('basket items')                //    instead of `PageElement`

Note that in the code sample above, selector By.css('#basket .item') makes the collection target both the <li class="item" /> elements, each of which containing two descendant elements: <span class="name" /> and <span class="price" /> .

In a moment, I'll show you how to make your queries more precise and retrieve only those elements you need.

Retrieving element from a collection​

If you need to retrieve a specific element from a collection, and you know what position it occupies, you can use PageElements#first(), PageElements#last(), and PageElements#nth(index) APIs:

import { By, PageElements } from '@serenity-js/web'

const firstItem = () =>
  PageElements.located(By.css('#basket .item'))
    .first()

const secondItem = () =>
  PageElements.located(By.css('#basket .item'))
    .nth(1)                                         // <- Note the zero-based indexing

const lastItem = () =>
  PageElements.located(By.css('#basket .item'))
    .last()

Above APIs are particularly useful when you need to retrieve elements from a sorted collection, such as the most recent comment under an article, the last customer order in a CRM system, nth position from a league table, and so on.

Retrieving text of multiple elements​

Similarly to PageElement, PageElements can be composed with other questions, like Text.ofAll:

import { By, PageElements, Text } from '@serenity-js/web'

const basketItemNameElements = () =>
  PageElements.located(By.css('#basket .item .name'))
    .describedAs('basket item names')

const basketItemNameElementNames = () =>
    Text.ofAll(basketItemNameElements())

Text.ofAll API is useful when you need to retrieve text content of multiple elements and assert on it all at once:

import { actorCalled } from '@serenity-js/core'
import { Ensure, equals } from '@serenity-js/assertions'
import { Text } from '@serenity-js/web'

await actorCalled('Alice').attemptsTo(
    Ensure.that(Text.ofAll(basketItemNameElements()), equals([
        'apples',
        'bananas',
    ]))
)

The trouble with duplicate selectors​

Note how in the last code sample we had to introduce a new function basketItemNameElements, which is almost the same as basketItems you saw earlier. The only real difference is that the new function makes the selector a bit more precise and helps us to return just the item name, and not the price:

const basketItems = () =>
  PageElements.located(By.css('#basket .item'))       // <- 
    .describedAs('basket items')                      //    Selectors are
                                                      //    _almost_  
const basketItemNameElements = () =>                  //    identical
  PageElements.located(By.css('#basket .item .name')) // <-
    .describedAs('basket item names')

To help you avoid duplicate selectors like the ones above, Serenity/JS page elements are designed to be composable and reusable through a mechanism called "meta-questions", which I'm about to show you next.

duplicate selectors increase maintenance costs

Having multiple almost identical but slightly different selector definitions in the same test suite (or even the same test!) is typically tolerated by software delivery teams due to poor support for code reuse offered by most test automation tooling.

However, this duplication also leads to increased maintenance costs. That's because even a small change to the structure of the UI might require you to fix multiple selectors in your test automation code. Not to mention the issue gets worse the more complex selectors you use.

Composing page elements using meta-questions​

Serenity/JS meta-questions are "questions about questions", so questions that can be composed with other questions and answered in their context. In short, any Serenity/JS question that has an question.of(anotherQuestion) API is a meta-question.

Conveniently, PageElement is a meta-question that can be composed with another PageElement using a declarative childElement.of(parentElement) API to dynamically model a descendant/ancestor (a.k.a. child/parent) relationship between the elements.

To improve our code from the last example and avoid duplicating element selectors, we can introduce functions called basketItem() and itemName() and compose them together as itemName().of(basketItem()):

import { actorCalled } from '@serenity-js/core'
import { By, PageElement } from '@serenity-js/web'
import { Ensure, equals } from '@serenity-js/assertions'

const basketItem = () =>
  PageElement.located(By.css('#basket .item')) // <- Note singular `PageElement` 
    .describedAs('basket item')

const itemName = () =>                         
  PageElement.located(By.css('.name'))         // <- Locator targeting  
    .describedAs('name')                       //    just the .name element

await actorCalled('Alice').attemptsTo(
  Ensure.that(
    Text.of(                                   // <- retrieve text of
        itemName().of(basketItem())            //    composed page elements   
    ),      
    equals('apples')    
  ),
)

Just like PageElement is a meta-question, PageElements is a MetaList that can be composed with another PageElement using a declarative pageElements.of(pageElement) API to dynamically model a descendants/ancestor (a.k.a. child/parent) relationship between the elements and their relative root element.

import { actorCalled } from '@serenity-js/core'
import { By, PageElement, Text } from '@serenity-js/web'
import { Ensure, equals } from '@serenity-js/assertions'

const basketItem = () =>
  PageElement.located(By.css('#basket .item')) // <- Note singular `PageElement` 
    .describedAs('basket item')

const itemNames = () =>                         
  PageElements.located(By.css('.name'))        // <- Note plural `PageElements`  
    .describedAs('name')

await actorCalled('Alice').attemptsTo(
  Ensure.that(
    Text.ofAll(                                // <- retrieve text of 
        itemNames().of(basketItem())           //    ALL the item names in one go   
    ),      
    equals([
        'apples',
        'bananas',
    ])    
  ),
)

Serenity/JS lets you compose not just the page elements, but also their descriptions. In our example, description of Text.of(itemName().of(basketItem())) will be derived from individual descriptions of questions in the chain and reported as text of name of basket item. Of course, you can set your own description if you prefer, too.

You might have also noticed that childElement.of(parentElement) API works only with individual elements. To map multiple elements we need to use PageElements mapping API we'll talk about next.

Serenity/JS PEQL helps you avoid code duplication

Serenity/JS PEQL lets you compose and reuse page element definitions, helping you to avoid code duplication and reduce maintenance costs.

Using meta questions to enable page element reuse can be a great productivity boost, especially when the system under test uses a consistent convention to name element identifiers and classes.

Mapping page elements in a collection​

Similarly to how you transform answers to individual questions, you can also transform each element in a collection using PageElements#eachMappedTo API and providing a meta-question to be used for the mapping.

For example, just how you'd use the meta-question about Text to retrieve the text value of an individual page element:

import { actorCalled } from '@serenity-js/core'
import { Ensure, equals } from '@serenity-js/assertions'
import { By, PageElement, Text } from '@serenity-js/web'

const basketItemName = () =>
  PageElement.located(By.css('#basket .item .name')) 
    .describedAs('basket item name')

await actorCalled('Alice').attemptsTo(
    Ensure.that(Text.of(basketItemName()), equals('apples'))
)

you could also use it to extract the text value of each element in a collection: 

import { actorCalled } from '@serenity-js/core'
import { Ensure, equals } from '@serenity-js/assertions'
import { By, PageElements, Text } from '@serenity-js/web'

const basketItemNames = () =>
  PageElements.located(By.css('#basket .item .name')) 
    .describedAs('basket item name')

await actorCalled('Alice').attemptsTo(
    Ensure.that(
        basketItemNames().eachMappedTo(Text),
        equals([ 
            'apples',
            'bananas',
        ])
    )
)

Where this pattern becomes indispensable is when you start reusing and composing several meta-questions together. For example, you could map each of basketItems() to retrieve their name or price:

import { actorCalled } from '@serenity-js/core'
import { Ensure, equals } from '@serenity-js/assertions'
import { By, PageElements, PageElement, Text } from '@serenity-js/web'

const basketItems = () =>
  PageElements.located(By.css('#basket .item'))   // <- plural PageElements
    .describedAs('basket items')

const itemName = () =>
  PageElement.located(By.css('.name'))            // <- singular PageElement
    .describedAs('name')

const itemPrice = () => 
  PageElement.located(By.css('.price'))           // <- singular PageElement
   .describedAs('price')

await actorCalled('Alice').attemptsTo(
  Ensure.that(
    basketItems().eachMappedTo(Text.of(itemName())),
    equals([ 
      'apples',
      'bananas'
    ])
  ),
  Ensure.that(
    basketItems().eachMappedTo(Text.of(itemPrice())),
    equals([
      '£2.25',
      '£1.50',
    ])
  )
)

Creating custom meta-questions​

Serenity/JS provides a number of meta-questions, like Text, CssClasses, or Attribute, and you can always write your own if needed.

For example, if you're dealing with a web interface that presents tabular data, you might want to fetch the table row, perform some transformation on each cell, then return the result as a JSON object so that it's easier to work with.

An equivalent of doing that in our example would be to:

  • retrieve the name and price of each basket item,
  • clean up the data,
  • transform it into a JSON object,
  • assert on the results.

You could implement the above as follows:


import { actorCalled, MetaQuestion, Question } from '@serenity-js/core'
import { Ensure, equals } from '@serenity-js/assertions'
import { By, PageElements, PageElement, Text } from '@serenity-js/web'

const basketItems = () =>                           // Locate basket item container elements
  PageElements.located(By.css('#basket .item'))
    .describedAs('basket items')

const BasketItemDetails: MetaQuestion<PageElement, Question<Promise<{ name: string, price: number }>>> = {
  
  of: (element: PageElement) =>    // A meta-qustion must provide a method called `of`

    Question.about('basket item details', async actor => {  // Create a question
    
       const name = Text                                  // Retrieve text of an element
           .of(PageElement.located(By.css('.name')))      // located by CSS class .name
           .of(element);                                  // within the container element
  
       const price = Text                                          // Retrieve text of an element
           .of(PageElement.located(By.css('.price')).of(element))  // located by CSS class .price
           .trim()                                                 // transform it to remove spaces
           .replace('£', '')                                       // remove the currency symbol
           .as(Number);                                            // convert the result to Number
  
       return {
           name:   await actor.answer(name),              // Instruct the actor to answer questions
           price:  await actor.answer(price),             // and return result as JSON object
       }
    })
}

await actorCalled('Alice').attemptsTo(
  Ensure.that(
    basketItems().eachMappedTo(BasketItemDetails),
    equals([
      { name: 'apples',  price: 2.25 },
      { name: 'bananas', price: 1.50 },
    ])
  ),
)

Alternatively, when you want to create a question that returns a JSON object, instead of using Question.about you can also use Question.fromObject, which will make your implementation more concise: 

const BasketItemDetails: MetaQuestion<PageElement, Question<Promise<{ name: string, price: number }>>> = {
    of: (element: PageElement) =>
      Question.fromObject({                             // Create a question that returns a JSON object
  
          name: Text                                        // Retrieve text of an element
              .of(PageElement.located(By.css('.name')))     // located by CSS class .name
              .of(element),                                 // within a container element
  
          price: Text                                                // Retrieve text of an element
              .of(PageElement.located(By.css('.price')).of(element)) // located by CSS class .price
              .trim()                                                // transform it to remove spaces
              .replace('£', '')                                      // remove the currency symbol
              .as(Number)                                            // turn the result into Number
  
      }).describedAs('basket item details')             // Provide custom description
}

Querying page elements​

While Serenity/JS expectations are most commonly used with assertion and synchronisation statements, when used with PageElements#where API they offer a great and reusable alternative to complex CSS selectors and XPath expressions.

In this section, I'll show you how to:

  • query page elements to find those that meet your expectations,
  • find an interactive element based on some property of its sibling,
  • iterate over selected elements to perform a common task.

In our examples, I'll be using a simple shopping list widget:

<ul id="shopping-list">
    <li class="item buy">
        <input type="checkbox" class="toggle">
        <label>oats</label>
        <button class="destroy">X</button>
    </li>
    <li class="item buy">
        <input type="checkbox" class="toggle">
        <label>coconut milk</label>
        <button class="destroy">X</button>
    </li>
    <li class="item bought">
        <input type="checkbox" class="toggle">
        <label>coffee</label>
        <button class="destroy">X</button>
    </li>
</ul>

I'm also going to introduce a couple of helper questions using the patterns and APIs you're already familiar with from the earlier parts of this chapter:

import { By, PageElement, PageElements } from '@serenity-js/web'

const shoppingList = () =>                              // Container element
    PageElement.located(By.id('shopping-list'))
        .describedAs('shopping list')

const shoppingListItems = () =>                         // Shopping list item 
    PageElements.located(By.css('.item'))               // widgets located within
        .of(shoppingList())                             // the shopping list container
        .describedAs('shopping list items')

const toggleButton = () =>                              // Toggle button
    PageElement.located(By.css('.toggle'))
        .describedAs('toggle')

const label = () =>                                     // Text of the item label
    Text.of(PageElement.located(By.css('label')))
        .describedAs('label')

const destroyButton = () =>                             // Destroy button
    PageElement.located(By.css('.destroy'))
        .describedAs('destroy button')

Filtering page elements​

Serenity/JS PageElements are a List, which means they offer a filtering API list.where(metaQuestion, expectation) and methods like first(), last(), or count().

You can use those APIs to find only those shopping list items that have buy within their CssClasses:

import { actorCalled } from '@serenity-js/core'
import { CssClasses } from '@serenity-js/web'

await actorCalled('Alice').attemptsTo(
    Ensure.that(
        shoppingListItems()
            .where(CssClasses, contain('buy'))
            .count(),
        equals(1)
    )
)

Furthermore, you can compose the result of your query with another question, like label().of(...): 

import { actorCalled } from '@serenity-js/core'
import { CssClasses } from '@serenity-js/web'
import { Ensure, contain, equals } from '@serenity-js/assertions'

await actorCalled('Alice').attemptsTo(
    Ensure.that(
        label().of(
            shoppingListItems()
                .where(CssClasses, contain('buy'))
                .last(),
        ),
        equals('coconut milk')
    )
)

You can also combine several .where calls, adding multiple meta-questions to your filter chain:

import { actorCalled } from '@serenity-js/core'
import { CssClasses } from '@serenity-js/web'
import { Ensure, contain, equals, includes } from '@serenity-js/assertions'

await actorCalled('Alice').attemptsTo(
    Ensure.that(
        label().of(
            shoppingListItems()
                .where(label(), includes('co'))     // 'coffee' and 'coconut milk'
                .where(CssClasses, contain('buy'))  // 'coffee'
                .first(),
        ),
        equals('coffee')
    )
)

You can also define a chain of filtering calls to resolve it dynamically in the context of a root element at runtime, improving reusability of your code:

import { actorCalled } from '@serenity-js/core'
import { Ensure, equals, isPresent } from '@serenity-js/assertions'

const itemCalled = (name: string) =>
    PageElements.located(By.css('.item'))
        .where(label(), equals(name))
        .first()
        .describedAs(`item called ${ name }`)   // note how we DON'T have to specify the container element

await actorCalled('Alice').attemptsTo(
    Ensure.that(
        itemCalled('coffee')
            .of(shoppingList()),                // container defined at runtime
        isPresent(),
    )
)

Finding a sibling element​

To find a sibling element, e.g. find a destroy button for an item which label contains a certain text:

  • find the container element which descendant element meets your conditions,
  • locate the sibling element within that container element.
import { actorCalled } from '@serenity-js/core'
import { CssClasses, Click } from '@serenity-js/web'
import { Ensure, contain, equals } from '@serenity-js/assertions'

const itemCalled = (name: string) =>
    shoppingListItems()                 // Container element where label
        .where(label(), equals(name))   // has certain text
        .first()

await actorCalled('Alice').attemptsTo(
    Click.on(
        destroyButton()
            .of(itemCalled('oats'))
    ),
)

Iterating over elements​

The List interface implemented by PageElements lets you use the List#forEach API to perform a sequence of interactions with each element of the collection.

For example, to toggle every item that hasn't been bought yet:

  • filter the list find elements that meet the expectation,
  • iterate over the found elements to click on the toggle button of each element.
import { actorCalled } from '@serenity-js/core'
import { CssClasses, Click } from '@serenity-js/web'
import { Ensure, contain, equals } from '@serenity-js/assertions'

await actorCalled('Alice').attemptsTo(
    shoppingListItems()
        .where(CssClasses, contain('buy'))
        .forEach(({ item, actor }) =>               // Note both `item` and `actor`:
            actor.attemptsTo(                       // `item` is the "current" element
                Click.on(toggleButton().of(item)),  // in the loop, `actor` is a reference
            )                                       // to the actor performing the task
        )
)