playwright-java

Topics in the source

• Playwright Java – Advanced Test Automation
• Overview
• When to Use This Skill
• How It Works
• Step 1: Decide the Approach
• Step 2: Scaffold the Project Structure
• Step 3: Set Up Thread-Safe BaseTest
• Step 4: Build Page Object Classes

This skill produces production-quality, enterprise-grade Playwright Java test code. It enforces the Page Object Model (POM), strict locator strategies, thread-safe parallel execution, and full Allure reporting integration. Targets Java 17+ and Playwright 1.44+. Supporting reference files are available for deeper topics: | Topic | File | |-------|------| | Maven POM, ConfigReader, Docker/CI setup | references/config.md | | Component pattern, dropdowns, uploads, waits | references/page-objects.md | | Full assertion API, soft assertions, visual testing | references/assertions.md | | Fixtures, test data factory, auth state, retry | references/fixtures.md | | Drop-in base class templates | templates/BaseTest.java, templates/BasePage.java | -- Use when scaffolding a new Playwright Java project from scratch Use when writing Page Object classes or JUnit 5 test classes Use when the user asks about cross-browser testing, parallel execution, or Allure reports Use when fixing flaky tests or replacing Thread.sleep() with proper waits Use when setting up Playwright in CI/CD pipelines (GitHub Actions, Jenkins, Docker) Use when combining API calls and UI assertions in a single test (hybrid testing

This is an excerpt. Refer to the complete source and its current requirements.