Browser profile management in Selenium Java - Framework Patterns

Framework Mode - Browser profile management

Folder Structure

src/
├── main/
│   └── java/
│       └── com/
│           └── example/
│               └── utils/
│                   └── BrowserProfileManager.java
├── test/
│   └── java/
│       └── com/
│           └── example/
│               ├── pages/
│               │   └── LoginPage.java
│               ├── tests/
│               │   └── LoginTest.java
│               └── utils/
│                   └── TestData.java
└── resources/
    ├── profiles/
    │   ├── chrome_profile/
    │   └── firefox_profile/
    └── config.properties

Test Framework Layers

• Driver Layer: Manages WebDriver setup with browser profiles using BrowserProfileManager.
• Page Objects: Classes representing UI pages, using WebDriver instances with profiles.
• Tests: Test classes that use page objects and driver layer to run tests with specific profiles.
• Utilities: Helper classes like BrowserProfileManager to load and configure browser profiles.
• Configuration: Properties files and resource folders to store profile paths and environment settings.

Configuration Patterns

• Profiles stored in resources/profiles/ folder for Chrome and Firefox.
• config.properties file holds keys like chrome.profile.path and firefox.profile.path.
• BrowserProfileManager reads config and loads profiles when creating WebDriver instances.
• Profiles can be switched by changing config or passing parameters to tests.
• Credentials and environment URLs stored separately and injected as needed.

Test Reporting and CI/CD Integration

• Use TestNG or JUnit reports to show test pass/fail with profile info in logs.
• Include browser profile details in test reports for traceability.
• Integrate with CI tools (Jenkins, GitHub Actions) to run tests with different profiles via parameters.
• Store profile artifacts and logs for debugging failed tests.

Best Practices

• Keep browser profiles outside source code in resource folders for easy updates.
• Use a dedicated utility class (BrowserProfileManager) to handle profile loading and WebDriver options.
• Parameterize tests to run with different profiles without code changes.
• Clean up or reset profiles between tests to avoid state leakage.
• Document profile usage clearly in config files and test documentation.

Self Check

Where in this folder structure would you add a new Firefox browser profile for testing a private browsing scenario?

Key Result

Manage browser profiles via a utility class and resource folder, enabling flexible WebDriver setup for tests.