ExpectedConditions class in Selenium Java - Framework Patterns

Framework Mode - ExpectedConditions class

Folder Structure

src
└── test
    └── java
        └── com
            └── example
                ├── pages
                │   └── LoginPage.java
                ├── tests
                │   └── LoginTest.java
                ├── utils
                │   └── WaitUtils.java
                └── config
                    └── TestConfig.java
    

This structure organizes page objects, tests, utilities, and configuration separately.

Test Framework Layers

• Driver Layer: Manages WebDriver setup and teardown.
• Page Objects: Classes representing web pages with locators and actions.
• Tests: Test classes using page objects and assertions.
• Utilities: Helper classes like WaitUtils that wrap ExpectedConditions for explicit waits.
• Configuration: Holds environment settings, browser options, and credentials.

The ExpectedConditions class is used in the Utilities layer to wait for specific conditions before interacting with elements.

Configuration Patterns

Use a TestConfig class or properties file to manage:

• Environment URLs (dev, staging, production)
• Browser types (Chrome, Firefox, Edge)
• Timeout durations for waits
• User credentials securely (avoid hardcoding)

Example snippet in TestConfig.java:

public class TestConfig {
    public static final String BASE_URL = System.getProperty("baseUrl", "https://example.com");
    public static final int EXPLICIT_WAIT_SECONDS = Integer.parseInt(System.getProperty("waitSeconds", "10"));
    public static final String BROWSER = System.getProperty("browser", "chrome");
}

Test Reporting and CI/CD Integration

• Use TestNG or JUnit reports for test execution results.
• Integrate Allure or ExtentReports for detailed HTML reports with screenshots.
• Configure CI/CD pipelines (Jenkins, GitHub Actions) to run tests on code commits.
• Fail fast on wait timeouts using ExpectedConditions to catch UI issues early.

Best Practices for Using ExpectedConditions

1. Use Explicit Waits: Always wait for elements or conditions before interacting to avoid flaky tests.
2. Wrap ExpectedConditions: Create utility methods (e.g., WaitUtils.waitForElementVisible(driver, locator)) to reuse waits and improve readability.
3. Avoid Thread.sleep(): Use ExpectedConditions instead of fixed waits for better performance and reliability.
4. Use Specific Conditions: Choose the right condition like visibilityOfElementLocated, elementToBeClickable, or presenceOfElementLocated based on test needs.
5. Set Reasonable Timeouts: Configure explicit wait timeouts to balance test speed and stability.

Self Check

Where in this folder structure would you add a new utility method that waits for an element to be clickable using ExpectedConditions?

Key Result

Use ExpectedConditions in utility classes to implement reliable explicit waits in Selenium Java frameworks.