FirefoxOptions configuration in Selenium Java - Framework Patterns

Framework Mode - FirefoxOptions configuration

Folder Structure

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

Test Framework Layers

• Driver Layer: Manages WebDriver setup and browser options (e.g., FirefoxOptions) in DriverFactory.java.
• Page Objects: Encapsulate web page elements and actions, e.g., LoginPage.java.
• Tests: Test classes using TestNG or JUnit, e.g., LoginTest.java.
• Utilities: Helper classes like configuration readers (ConfigReader.java).
• Configuration: Central place for environment and browser settings, used by Driver Layer.

Configuration Patterns

Use a properties file (e.g., config.properties) to store environment URLs, browser types, and credentials.

Example properties:

browser=firefox
headless=true
baseUrl=https://example.com

In DriverFactory.java, read these properties and configure FirefoxOptions accordingly:

import org.openqa.selenium.firefox.FirefoxOptions;

public class DriverFactory {
    public static FirefoxOptions getFirefoxOptions(boolean headless) {
        FirefoxOptions options = new FirefoxOptions();
        if (headless) {
            options.addArguments("-headless");
        }
        // Add other options as needed
        return options;
    }
}

Test Reporting and CI/CD Integration

• Use TestNG or JUnit reports for test results.
• Integrate with CI tools like Jenkins or GitHub Actions to run tests on code changes.
• Configure reports to show browser and environment details (e.g., Firefox version, headless mode).
• Store screenshots on failure for debugging.

Best Practices

1. Centralize browser options: Keep FirefoxOptions setup in one place (DriverFactory) to avoid duplication.
2. Use configuration files: Control headless mode and other options without code changes.
3. Explicit waits: Use waits to handle dynamic page elements instead of fixed sleeps.
4. Page Object Model: Separate page logic from tests for maintainability.
5. Clean driver lifecycle: Properly start and quit WebDriver to avoid resource leaks.

Self Check

Where in this folder structure would you add a new method to configure FirefoxOptions for running tests in private browsing mode?

Key Result

Centralize FirefoxOptions configuration in a DriverFactory class using properties for flexible browser setup.