🌐 Language / Idioma
🇬🇧 English | 🇪🇸 Español
Enterprise-ready E2E automation framework built with Playwright for Java, JUnit 5, and Maven, designed to showcase scalable QA automation design, maintainability, clean architecture, and reporting readiness.
This repository is positioned as a QA Automation portfolio project that demonstrates more than automated checks. It shows how to structure a maintainable Java-based framework with:
- Playwright for Java for modern browser automation
- JUnit 5 for structured test execution
- Maven for dependency and build management
- Page Object Model (POM) for clean abstraction and reuse
- Allure reporting for execution evidence
- Logging and reusable utilities for maintainability
- Tag / group-based execution strategy
- Scalable architecture ready to evolve toward CI/CD
This project demonstrates Java QA automation best practices, including maintainable architecture, reporting, reusable components, and structured documentation.
This repository contains an end-to-end automation framework for SauceDemo using:
- Playwright for Java
- JUnit 5
- Maven
- Allure Report
- Page Object Model
- Log4j / SLF4J logging
- DataFaker-based test data support
🔗 Application under test: https://www.saucedemo.com/
🔗 Repository: https://github.com/CarlosArman/PlaywrightJava
- ✅ Login validation
- ✅ Shopping validation
- ✅ Item detail coverage
- ✅ Footer coverage
- ✅ Burger menu coverage
- ✅ Cart coverage
- ✅ Checkout information coverage
- ✅ Java + JUnit 5 based automation design
- ✅ Page Object Model architecture
- ✅ Reusable utilities and shared flows
- ✅ Group-based execution support
- ✅ Allure-ready reporting
- ✅ Structured logging configuration
- ✅ Clean separation between tests, pages, models, utilities, and data
- ✅ Clean automation architecture in the Java ecosystem
- ✅ Practical evidence generation strategy
- ✅ Clear documentation and project organization
- ✅ Easy onboarding for reviewers and recruiters
- ✅ Strong comparison point against a TypeScript + Cucumber implementation
- Language: Java 17+
- Automation Framework: Playwright for Java
- Testing Framework: JUnit 5
- Build Tool: Maven
- Design Pattern: Page Object Model (POM)
- Reporting: Allure Results / Allure Report
- Logging: Log4j / SLF4J
- Test Data: DataFaker
- Application Under Test: SauceDemo
PlaywrightJava
├── src/
│ ├── main/
│ │ ├── java/
│ │ └── resources/ # Main resources and global configuration
│ └── test/
│ ├── java/
│ │ ├── annotations/ # Custom annotations and execution groups (e.g. Smoke, Regression)
│ │ ├── automation/ # Test classes and automated scenario coverage
│ │ ├── data/ # Test data builders and custom data providers
│ │ ├── models/ # Domain and test data models
│ │ ├── pages/ # Page Object Model and reusable UI components
│ │ └── utilities/ # Base classes, common flows, providers, logging, and utilities
│ └── resources/ # Test resources and execution/report configuration
├── docs/ # Additional documentation
├── CHANGELOG.md # Project changelog
├── CONTRIBUTING.md # Contribution guide
├── pom.xml # Maven build, dependencies, and plugin configuration
├── README.md # Main documentation in English
└── README.es.md # Main documentation in Spanishgit clone https://github.com/CarlosArman/PlaywrightJava.git
cd PlaywrightJavamvn clean installmvn exec:java -Dexec.mainClass=com.microsoft.playwright.CLI -Dexec.args="install"mvn clean testThe main README should expose only the most important commands. For the full reference, see docs/COMMANDS.md and * *docs/COMMANDS.es.md**.
mvn clean install
mvn exec:java -Dexec.mainClass=com.microsoft.playwright.CLI -Dexec.args="install"
mvn clean test
mvn clean test -Dgroups="login"
allure serve allure-resultsThis framework includes execution evidence through:
- JUnit 5 execution results
- Allure results generation
- Allure HTML visualization
- Logging configuration through Log4j / SLF4J
- Structured page abstractions and shared flows for debugging clarity
To open the report after execution:
allure serve allure-resultsThe framework is organized around separation of concerns:
automation/→ test classespages/→ UI interaction abstractionutilities/→ base classes, shared flows, logging, and providersmodels/→ domain modelsdata/→ reusable/custom data supportannotations/→ grouping or categorization strategyresources/→ configuration artifacts such aslog4j2.xmlandallure.properties
For full architecture details, see:
If you would like to compare this framework with a related automation project built in the TypeScript ecosystem, check out:
A related implementation built with:
- TypeScript
- Playwright
- Cucumber (BDD)
- Allure Report
- Page Object Model (POM)
This comparison demonstrates the ability to work across both Java + JUnit 5 and TypeScript + Cucumber stacks while preserving strong QA automation architecture principles.
- docs/COMMANDS.md → Commands reference (English)
- docs/COMMANDS.es.md → Commands reference (Spanish)
- docs/ENVIRONMENT.md → Environment guide (English)
- docs/ENVIRONMENT.es.md → Environment guide (Spanish)
- docs/ARCHITECTURE.md → Architecture guide (English)
- docs/ARCHITECTURE.es.md → Architecture guide (Spanish)
- CHANGELOG.md → Project changelog (English)
- CHANGELOG.es.md → Historial de cambios (Español)
- CONTRIBUTING.md → Contribution guide (English)
- CONTRIBUTING.es.md → Guía de contribución (Español)
- Expand scenario coverage
- Add stronger group strategy documentation
- Strengthen CI/CD integration
- Add richer evidence examples in the repository
- Improve metrics / observability conventions
Carlos R.
QA Test Automation Engineer
🔗 GitHub: https://github.com/CarlosArman
This project is intentionally documented and structured to reflect not only functional automation capability, but also * engineering maturity in Java-based QA automation design*.