Java Playwright End-to-End Framework
Budget: $8 – $15 USD
I need a clean, maintainable automation framework in Java, built on Playwright, that lets me run full end-to-end tests of my web application in Chrome. The framework should embrace good engineering practices—clear page objects, readable test cases, reusable helpers, and straightforward configuration—so my team can extend coverage quickly as the product evolves.
Core coverage for the first sprint:
• User login flow, including validation of both valid and invalid credentials
• Payment process from cart to confirmation, with verification of transaction results and error handling paths
• Search functionality, checking result accuracy, filters, and pagination
Please wire in concise HTML or JUnit‐style reports, an example GitHub Actions (or similar) workflow for CI execution, and a short README that explains how to set up, run, and add new tests. Pass/fail results must be deterministic and reproducible on a fresh clone.
Acceptance criteria
• All tests execute headless in Chrome via a single Maven/Gradle command
• Clear folder structure separating tests, pages, data, and utilities
• Build completes with zero warnings and all assertions correctly evaluated
• Reports generated automatically in the build output directory
Hand over the full project as a ZIP or Git repository link when done, and I’ll take it from there.
Core coverage for the first sprint:
• User login flow, including validation of both valid and invalid credentials
• Payment process from cart to confirmation, with verification of transaction results and error handling paths
• Search functionality, checking result accuracy, filters, and pagination
Please wire in concise HTML or JUnit‐style reports, an example GitHub Actions (or similar) workflow for CI execution, and a short README that explains how to set up, run, and add new tests. Pass/fail results must be deterministic and reproducible on a fresh clone.
Acceptance criteria
• All tests execute headless in Chrome via a single Maven/Gradle command
• Clear folder structure separating tests, pages, data, and utilities
• Build completes with zero warnings and all assertions correctly evaluated
• Reports generated automatically in the build output directory
Hand over the full project as a ZIP or Git repository link when done, and I’ll take it from there.
Related categories:
PHP
Business, Accounting, Human Resources & Legal
JavaScript
Software Architecture
JUnit
Selenium
Automation
CI/CD