playwright-java

Add the com.microsoft.playwright dependency and JUnit 5 to your Maven pom.xml, then create a BaseTest class that manages Playwright, Browser, BrowserContext, and Page instances in @BeforeEach and @AfterEach hooks. Run mvn exec:java with the Playwright CLI to install browsers.

Enable parallel execution in junit-platform.properties with junit.jupiter.execution.parallel.enabled=true and concurrent mode. Each test must create its own Playwright-to-Page chain via ThreadLocal variables, since sharing a Page across threads causes random failures.

Playwright is preferred for new projects because its locator assertions auto-retry until timeout, eliminating most explicit waits. It also provides built-in tracing, video recording, network mocking, and a single API across Chromium, Firefox, and WebKit.

Flakiness in parallel mode usually comes from sharing a Page or BrowserContext across threads. Store Playwright, Browser, BrowserContext, and Page in ThreadLocal fields so each test thread gets an isolated browser instance.

Replace Thread.sleep with auto-retrying assertions like assertThat(locator).hasText(), or use page.waitForResponse() to wait for specific API calls. Playwright assertions poll automatically until the condition is met or the timeout expires.

A blank Allure report usually means the AspectJ weaver agent is missing from the maven-surefire-plugin argLine configuration. Add the -javaagent entry pointing to aspectjweaver in your local Maven repository as shown in the pom.xml configuration.