How oktaliem/pageobjectpagefactoryactions works
Project type and purpose
• This is a Maven-based Java test automation framework.
• It implements a keyword-driven approach around Selenium WebDriver, using both Page Object and Page Factory patterns.
• Purpose: wrap WebDriver calls into reusable “keywords” (clickOn, sendKeys, waitFor, etc.), organize UI locators and actions in page classes, and execute tests via TestNG.
a. Test Runner Layer
• Maven + Surefire plugin
• TestNG (TestNG.xml)
b. Test Suite Layer
• com.oktaliem.testsuite.* classes (UnitTest, AngularTest, ReactTest, etc.)
• BaseTest class (initializes WebDriver, sets up test context)
c. Keyword Library & Page Layer
• Page Objects (src/test/java/com/oktaliem/pages/*)
• Page Factory classes (annotated @FindBy)
• Interfaces for actions (IElementActions, IWaitActions, etc.)
• Concrete base-action implementations (BaseElementAct, BaseWaitAct, BaseJSExecutorAct, etc.)
d. WebDriver Manager & Driver Binaries
• WebDriverManager integration (downloads drivers automatically)
• Manual binaries under /drivers (chromedriver-*) as fallback
e. Web Browser & SUT (System Under Test)
• ChromeDriver → Chrome browser (or other browser)
• Web application under test (e.g., Bitnami Odoo container)
f. Logging & Configuration
• log4j.properties (src/test/resources)
• actualhtmltext artifacts (for text-based verification)
Relationships and data flow
• The Maven/TestNG runner loads TestNG.xml → invokes Test Suite classes.
• Each Test Suite class extends BaseTest → requests a WebDriver instance (via WebDriverManager or binary).
• WebDriver instance is passed into Page Factory / Page Object constructors.
• Test methods call “keyword” methods (clickOn, typeOn, waitUntil, etc.) on page objects; these methods delegate to base-action classes.
• Base-action classes invoke the WebDriver API (findElement, executeScript, takeScreenshot, etc.).
• WebDriver controls the browser → interacts with the SUT → returns control/data to test code.
• All keyword calls emit log entries via log4j.
Architectural patterns & design principles
• Layered design:
Test Runner → Test Suites → Page Objects/Factory → Base Actions → WebDriver → Browser/SUT
• Page Object Model + Page Factory for locator encapsulation and code re-use.
• Keyword-driven: exposes high-level actions rather than raw WebDriver calls.
• Dependency injection via BaseTest: supplies WebDriver to pages.
• Configuration via Maven profiles, system properties, and log4j.
• Use clear, consistent labels for classes or packages (e.g., com.oktaliem.pages, com.oktaliem.pages.baseactions).
• Related classes (pages, actions, tests) inside containers to reduce clutter.