Support Playwright

Playwright is “a Node.js library to automate Chromium, Firefox and WebKit with a single API” that now also supports Java. Let’s see how we can best integrate it with JUnit Jupiter.

One thing to note is that we should keep the dependency on Playwright optional (aka provided), so we don’t drag it in ourselves if users don’t already use it. It should probably also be in its own package org.junitpioneer.(jupiter.?)playwright. If it proves successful and grows, we can always spin it out into its own project by moving the package there.

In this issue, let’s collect and discuss ideas. For their implementation, we can create dedicated issues.

My only idea so far:

• parameter resolver that injects Browser instances, so tests can easily be executed against multiple browsers

[beatngu13]

One thing to note is that we should keep the dependency on Playwright optional (aka provided), so we don’t drag it in ourselves if users don’t already use it.

Rather than using provided, how about optional (Maven) / feature variants (Gradle)? Haven’t used these myself, but it sounds exciting! (Related blog post.)

If it proves successful and grows, we can always spin it out into its own project by moving the package there.

junit-pioneer-playwright, junit-pioneer-selenium, … 👏

[nipafx]

I’m pretty sure, I’ve already written an extension like this for Selenium, but I can’t find it. No idea where that one went. I dimly remember opening a PR somewhere… 🙈