findElement by ID in Selenium Java - Framework Patterns

Framework Mode - findElement by ID

Folder Structure

src/
└── test/
    └── java/
        └── com/
            └── example/
                ├── pages/
                │   └── LoginPage.java
                ├── tests/
                │   └── LoginTest.java
                ├── utils/
                │   └── WebDriverFactory.java
                └── config/
                    └── ConfigReader.java

Test Framework Layers

• Driver Layer: Manages WebDriver setup and teardown (e.g., WebDriverFactory.java).
• Page Objects: Classes representing pages with locators and methods using findElement(By.id()) to interact with elements (e.g., LoginPage.java).
• Test Layer: Test classes that use page objects to perform test scenarios (e.g., LoginTest.java).
• Utilities: Helper classes for common functions like waits, logging, or reading configs.
• Configuration: Handles environment variables, browser settings, and credentials (e.g., ConfigReader.java).

Configuration Patterns

• Use config.properties or application.properties files to store environment URLs, browser types, and credentials.
• ConfigReader.java reads these properties and provides access to tests and page objects.
• Use system properties or environment variables to override defaults for CI/CD pipelines.
• Example: browser=chrome, baseUrl=https://example.com, username=testuser.

Test Reporting and CI/CD Integration

• Use TestNG or JUnit test runners with built-in reporting.
• Integrate with reporting tools like Allure or ExtentReports for detailed HTML reports.
• Configure CI/CD pipelines (Jenkins, GitHub Actions) to run tests on code push and publish reports.
• Use screenshots on failure captured in page objects or test listeners.

Best Practices

1. Use Page Object Model: Keep locators and actions in page classes to separate test logic from UI details.
2. Use By.id() for Locators: IDs are unique and fast for locating elements.
3. Explicit Waits: Use WebDriverWait to wait for elements by ID to be visible or clickable before interacting.
4. Centralize Configuration: Manage environment and browser settings in one place for easy changes.
5. Clean Folder Structure: Organize code by layers (pages, tests, utils, config) for maintainability.

Self Check

Where in this folder structure would you add a new page object class for a "Dashboard" page that uses findElement(By.id()) to locate elements?

Key Result

Organize Selenium Java tests using Page Object Model with unique ID locators and centralized configuration.