Generate Enterprise Playwright Java Test Automation Code

This skill scaffolds, writes, and diagnoses Playwright end-to-end tests in Java. It organizes browser interactions through the Page Object Model and JUnit 5 test classes, with guidance for isolated parallel execution, cross-browser runs, API-and-UI scenarios, and Allure reports. The stated targets are Java 17 or later and Playwright 1.44 or later.

The workflow chooses an approach before creating code: a full project scaffold, one page object and feature test, a hybrid API/UI scenario, a browser-parameterized test, or a focused flaky-test repair. Project organization separates base classes, page classes, scenarios, utilities, configuration, resources, and test data. Reference files and BaseTest and BasePage templates support the detailed implementation.

Page objects declare locator fields separately from action methods and prefer role, label, or test-ID selectors. Navigation methods return the next page object for fluent use. Tests use retrying locator assertions and soft assertions when checking multiple fields. Fixed sleeps are replaced with response waits, element waits, or assertions that poll for the required state.

Use it for a new Playwright Java suite, page-object implementation, cross-browser coverage, parallel execution, rich diagnostics, or CI integration. It also fits cases where an API creates test data that is then verified through the interface, or a network failure must be simulated to check error handling.

It warns against sharing a Page between threads, creating Playwright instances inside page objects, hardcoding base URLs, and using XPath for frequently changing elements. Missing permissions or success criteria require clarification. The generated suite needs validation in its actual environment rather than relying on the examples alone.

Inputs include application URLs, test scenarios, browser choices, configuration, test data, and authentication requirements. Outputs can include a Maven project structure, base classes, page objects, JUnit scenarios, saved authentication setup, reporting configuration, and pipeline instructions.

Each test's isolated browser chain is maintained with ThreadLocal values for Playwright, Browser, BrowserContext, and Page. Setup initializes the chain and starts tracing; teardown writes a trace file and closes resources. The example includes video recording and locale configuration. Parallelism is controlled through junit-platform.properties, illustrated by:

junit.jupiter.execution.parallel.enabled=true

Diagnostics address timeouts, absent traces, missing report steps, and stale storageState authentication. Trace recording must start before actions and stop during each test's teardown. Report instrumentation can require AspectJ configuration, and saved authentication may need regeneration before the suite.

The skill combines Playwright Java, JUnit 5, Maven, Allure, AspectJ, and configuration utilities. Browser coverage includes Chromium, Firefox, and WebKit. APIRequestContext supports hybrid setup, route interception supplies network mocks, and storageState allows login reuse.

CI examples install browsers with dependencies, run headless tests, and upload failure traces and Allure results in GitHub Actions. Jenkins and Docker are also named integration contexts. Supporting references cover configuration, page components and waits, assertion patterns including visual checks, fixtures, data factories, authentication, and retries. Related skills cover REST Assured, Selenium, Allure, Testcontainers, and complete browser-matrix workflows.

It serves developers maintaining Java browser-test suites who need reusable interactions and reliable diagnostics. It also supports teams combining API setup with UI assertions and running tests across browsers or concurrently.