4 posts tagged with "webdriverio"

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!

📣 Serenity/JS now supports tagging across all the test runners 🎉

With the new release of Serenity/JS 3.21, tagging test scenarios just got easier. Now, you can use @tags across all the supported test runners, so:

• Cucumber
• Jasmine
• Mocha
• WebdriverIO
• Playwright Test
• Protractor

Why should you tag your scenarios?​

Tagging test scenarios helps you organise and filter your test suites. You can categorise tests based on functionality, priority, or type, making it easier to manage and focus your testing efforts.

Plus, tagging allows for selective test execution. You can run a subset of tests by specifying relevant tags, which is handy for regression testing or when focusing on specific parts of your application.

Tagging also improves test reporting and integrates well with test management tools. It gives you insights into test coverage and helps streamline test planning and tracking.

And if you're using Playwright Test, Serenity/JS supports the latest Playwright 1.42 tag API, enhancing your tagging capabilities even further!

Contributor spotlight​

A huge thank you to our Serenity/JS Contributors for their work on this release:

• Otoniel Isidoro, who enabled tagging support for Playwright Test
• Mateusz Kruk, who greatly improved Playwright Test global error handling

Enjoy Serenity!

Serenity/JS 3.15.0 introduces support for Serenity BDD 4 and aggregated test reports for Playwright Test, WebdriverIO, Mocha, Jasmine and Cucumber! 🥳

We've also updated the Serenity/JS Handbook to help you get the most out of the new Serenity/JS and Serenity BDD reporting features - check out:

• Reporting > Serenity BDD Reporter
• Serenity BDD Best Practices (NEW!)

Important changes​

If you're still using the Serenity/JS 2-style syntax for registering the SerenityBDDReporter, you'll need to update your configuration file to use the Serenity/JS 3 convention:

- import { ArtifactArchiver } from '@serenity-js/core';
- import { SerenityBDDReporter } from '@serenity-js/serenity-bdd';

// ...
    crew: [
-     new SerenityBDDReporter(),
-     ArtifactArchiver.storingArtifactsAt('./target/site/serenity'),
+     '@serenity-js/serenity-bdd',
+     [ '@serenity-js/core:ArtifactArchiver', {
+       outputDirectory: 'target/site/serenity'
+     } ],
    ]
// ...

Learn more about Configuring Serenity BDD Reporter.

Serenity/JS started to support WebdriverIO in version 2.30.0.

In version 3.0.0, Serenity/JS brought you @serenity-js/web - a portable abstraction layer that lets you run the exact same web scenario with WebdriverIO, Playwright, and even Protractor!

Now, we're taking things further with Serenity/JS 3.2.0 introducing support for the latest and greatest WebdriverIO 8! 🥳

Check out our new tutorial where in less than 5 minutes, you'll learn how to integrate Serenity/JS with your WebdriverIO test suite, enable Serenity BDD reports, and start using the Screenplay Pattern!

Learn about Using Serenity/JS with WebdriverIO!