15 posts tagged with "web"

Serenity/JS 3.49 makes your scenarios faster without you changing a line of code. Actors used to spend at least 10 milliseconds after every Interaction and Task waiting for background work, such as taking screenshots, even when there wasn't any. Now they move on as soon as the work is done, or straight away when there's nothing to wait for. The more activities a scenario performs, the more time it saves. This release also teaches web Interactions such as Click and Enter to wait for list items that haven't been rendered yet, and makes By.role() in @serenity-js/playwright match exactly the same elements as Playwright's own getByRole().

Two of these changes can affect existing test suites, so read the upgrade notes before you update.

Serenity/JS 3.47 brings web UI component testing into the same Screenplay Pattern architecture as the rest of your suite. The new story fixture mounts a Playwright component story, and the newly introduced Question.as(Constructor) lets you turn it into an Interaction Object.

That means the interaction model you use to exercise the component in isolation can be the same one your end-to-end scenarios use when exercising the running application.

This release also introduces new guides to help you set up component testing and keep your web test code portable with Serenity/JS web modules.

Serenity/JS 3.46 extends PageElement to enable fluent child element access and introduces a new design pattern — Interaction Objects — for modelling UI components through composable Questions and Tasks.

Together, these features make it easier to structure your test code around what users can observe and do, rather than the underlying DOM structure.

Jan Graefe recently published an open letter in response to the updated Getting Started guides on serenity-js.org. His letter touches on something that's been central to the Screenplay Pattern since 2007 — and that I've been working on since joining the effort in 2013: the idea that test automation should express intent, not implementation.

I'd like to respond publicly because the ideas Graefe raises deserve a wider conversation.

Serenity/JS 3.43 introduces support for testing Electron desktop applications using the same Screenplay Pattern APIs you already know from web testing. This release also brings a completely revamped Playwright Test documentation — split into focused, digestible guides to help you get productive faster.

Let's explore what's new!

Serenity/JS 3.37 introduces a focused set of improvements to the Playwright Test integration, delivered in PR #3096. This update strengthens the flexibility of Playwright Test fixtures while keeping the Serenity/JS API clean, expressive, and easy to maintain.

Let's explore what's new!

The latest release, Serenity/JS 3.32, brings powerful enhancements to your test automation workflow. This version focuses on further improving the integration between Playwright Test and Serenity BDD, delivering rich, actionable test reports that go beyond pass/fail results.

Key updates in this release:

🎭 Improved APIs and support for using actors in beforeAll and afterAll hooks.

✅ Improved reporting, including support for retried tests, repeated tests, and project tags.

⚙ Configuration updates to better separate test-scope and worker-scope fixtures.

Let’s take a closer look at what’s new!

We’re thrilled to announce the release of Serenity/JS 3.31, marking a significant step forward for modern test automation. This release introduces support for WebdriverIO 9, while maintaining compatibility with WebdriverIO 8 for projects that are not yet ready to migrate (#2572).

Let’s explore what makes this update exciting!

Love numbers? You'll love Serenity/JS 3.29! 🎉

We’re excited to share the latest release of Serenity/JS, which is packed with new powerful features for handling numeric data in your automated tests!

In the ever-evolving world of software development, the importance of clear, concise, and accessible documentation cannot be overstated. The Serenity/JS team is thrilled to announce a series of significant improvements to our API documentation, designed to enhance the developer experience and streamline the process of building automated acceptance tests. These updates are crafted to support developers at every stage of their journey, from understanding the basics to mastering the intricacies of the framework.