How tahanima/playwright-java-test-automation-architecture works
Main Components
a) Core Test Framework Layer:
• Test Execution Engine (JUnit 5)
• Configuration Management
• Browser Management
• Test Data Management
• Reporting System (Allure)
b) Page Object Layer:
• Page Objects
• Component Objects
• Page Factory
c) Test Implementation Layer:
• E2E Tests
• Test Utilities
• Data Transfer Objects (DTOs)
• ┌─────────────────────────────────────────┐
• Test Implementation │
• (E2E Tests, Annotations, Test Utils) │
• ┤
• Page Object Architecture │
• (Page Objects, Components, Factory) │
• ┤
• Core Framework │
• (Browser, Config, Data Management) │
• ┘
Component Relationships
a) Data Flow:
• Test Data (CSV) → DTOs → Test Classes
• Configuration → Browser Factory → Page Objects
• Test Execution → Allure Reporting
b) Dependencies:
• Page Objects → Component Objects
• Tests → Page Objects
• Browser Factory → Playwright
Detailed Component Breakdown
Specific components from the project:
Core Framework:
• Configuration (Configuration.java, ConfigurationManager.java)
• Browser Management (BrowserManager.java, BrowserFactory.java)
• Data Management (CsvToDtoMapper.java, DataArgumentsProvider.java)
Page Objects:
• Base Classes (BasePage.java, BaseComponent.java)
• Page Implementations (LoginPage.java, ProductsPage.java)
• Components (Header.java, SideNavMenu.java)
Test Implementation:
• Base Test (BaseTest.java)
• Test Classes (LoginTest.java, ProductsTest.java)
• DTOs (LoginDto.java, ProductsDto.java)
• Annotations (@DataSource, @Regression, @Smoke, @Validation)
External Dependencies
Integration points with:
• Playwright
• JUnit 5
• Allure Reporting
• Univocity Parsers
• Lombok