#Serenity 2 how to#
#Serenity 2 portable#
#Serenity 2 code#

SERENITY II has been designed to comfortably accommodate up to 12 charter guests in 6 suites. The 131ft / 40m SERENITY II has been constructed with a steel hull and is powered by 2x CAT C32 1115hp 2100 RPM with a cruising speed of 12 knots and a top speed of 15 knots. The exterior of SERENITY II is designed by Endaze Mühendislik. The luxury motor yacht SERENITY II was built by Mengi-Yay and delivered to her owner in 2010, she later underwent a refit in 2021. How does it work? In Serenity 3, calling BrowseTheWeb.as(actor) looks up any ability that extends the base BrowseTheWeb, so currently either BrowseTheWebWithWebdriverIO, BrowseTheWebWithProtractor, or your custom extensions of those classes.SERENITY II currently registered in Malta is actively available for charter. Note that this also means that there's a good chance that any custom interactions and questions you have implemented with Serenity/JS 2 would still work with few if any changes with Serenity/JS 3.

#Serenity 2 portable#

Implementing portable Interactions and Questions īecause BrowseTheWebWithWebdriverIO extends BrowseTheWeb, any custom interactions and questions should still use the generic and tool-agnostic BrowseTheWeb from to be portable between the different integration tools.

#Serenity 2 how to#

Learn how to configure a custom cast of actors with: However, if the default configuration is not sufficient to your needs,Įvery test runner integration still lets you configure a custom cast. BrowseTheWeb, using the test runner-specific implementation of BrowseTheWeb.

The default Cast provides actors where each actor has the abilities to: The first change you'll see is in how the Actors class is defined.ĭefault cast of actors provided by Serenity/JS v3 can help you to avoid having to specify a custom cast altogether. That's because while your tests can be agnostic of the lower-level integration tool, the Actors need to 'know' what tool to use. The only non-portable part of Serenity/JS 3.x Web tests is your Actors class. To see what the changes look like in practice, have a look at the TodoMVC tests implemented using:

#Serenity 2 code#

This change will help your test code be much more portable between the different integration tools, and will also help us significantly reduce the effort of introducing new integrations (with support for Playwright already in the works). The new module contains all the Web-related interactions and questions, while the integration-tool specific modules such as and contain only tool-specific models and abilities. The most significant change in the Web testing space is the introduction of the module and numerous features that help your tests become portable across the different test integration tools (such as Protractor, WebdriverIO, Puppeteer, etc.)

serenity-js-mocha-webdriverio-template ( see diff).

serenity-js-cucumber-webdriverio-template ( see diff).

We've already migrated several of the popular Serenity/JS templates, and you'll find code using the new Serenity/JS APIs on the main branch (the old 2.x branch still contains Serenity/JS 2 code): Will help you get started and highlight notable differences from Serenity/JS version 2. The latest Release Candidate (RC) is already available on NPM and this guide Serenity/JS 3.0 introduces a number of new features while aiming to retain backwards compatibility of most of the core APIs.