Hybrid framework architecture in Selenium Java - Framework Patterns

Framework Mode - Hybrid framework architecture

Folder Structure

project-root/
├── src/
│   ├── main/
│   │   └── java/
│   │       └── com/example/app/
│   │           └── (application source code)
│   └── test/
│       └── java/
│           └── com/example/tests/
│               ├── base/               # Base classes (TestBase, DriverManager)
│               ├── pages/              # Page Object classes
│               ├── tests/              # Test classes (TestNG/JUnit)
│               ├── utils/              # Utility classes (helpers, data readers)
│               └── data/               # Test data files (Excel, JSON)
├── resources/
│   ├── config.properties               # Configuration file
│   └── testdata/                       # External test data files
├── testng.xml                         # TestNG suite configuration
├── pom.xml                            # Maven build file
└── README.md
    

Test Framework Layers

• Driver Layer: Manages WebDriver setup, browser initialization, and teardown.
• Page Object Layer: Contains page classes representing UI pages with locators and actions.
• Test Layer: Test classes that use page objects and test data to perform test scenarios.
• Utility Layer: Helper classes for reading test data, logging, waits, and reusable methods.
• Configuration Layer: Holds environment settings, browser types, URLs, and credentials.

Configuration Patterns

Use a config.properties file to store environment variables like URLs, browser types, and credentials.

Example config.properties:

url=https://example.com
browser=chrome
username=testuser
password=testpass
    

Load properties in a utility class to access configuration values.

Use Maven profiles or system properties to switch environments (dev, test, prod) during test execution.

Test Reporting and CI/CD Integration

• Use TestNG built-in reports and extend with ExtentReports for detailed HTML reports with screenshots.
• Integrate with CI/CD tools like Jenkins or GitHub Actions to run tests automatically on code commits.
• Configure test reports to be archived and emailed after test runs.
• Use logs and screenshots on failure to help debugging.

Best Practices for Hybrid Framework

1. Combine Keyword-Driven and Data-Driven Testing: Use keywords to define test steps and external data files to drive test inputs.
2. Use Page Object Model: Keep UI locators and actions separate from test logic for easy maintenance.
3. Centralize Configuration: Manage environment and browser settings in one place for flexibility.
4. Implement Reusable Utilities: Create helper methods for common tasks like waits, logging, and data reading.
5. Keep Tests Independent: Each test should run alone without relying on others to avoid flaky results.

Self Check

Where in this folder structure would you add a new page object class for the Login page?

Key Result

Hybrid framework combines keyword-driven and data-driven testing with Page Object Model for maintainable, flexible automation.

Practice

1. What is the main advantage of using a Hybrid framework in Selenium Java testing?

easy

A. It combines keyword-driven and data-driven approaches for better flexibility.

B. It only uses data-driven testing for faster execution.

C. It requires no coding knowledge to create tests.

D. It runs tests only on a single browser.

Solution

1. Step 1: Understand Hybrid framework components

   A Hybrid framework mixes keyword-driven and data-driven testing methods to leverage benefits of both.

2. Step 2: Identify the advantage

   This combination allows flexible test design and easier maintenance, improving test reuse and scalability.

3. Final Answer:

   It combines keyword-driven and data-driven approaches for better flexibility. -> Option A

4. Quick Check:

   Hybrid framework = combines keyword + data-driven [OK]

Hint: Hybrid = mix keyword + data-driven testing [OK]

Common Mistakes:

• Thinking hybrid uses only one testing approach
• Assuming hybrid requires no coding
• Believing hybrid limits browser support

2. Which of the following is the correct way to organize test data in a Hybrid framework?

easy

A. Write test data directly in the Selenium WebDriver code.

B. Hardcode test data inside test scripts.

C. Store test data in external files like Excel or CSV.

D. Use random values generated during test execution.

Solution

1. Step 1: Recall data-driven testing principle

   Data-driven testing stores test data externally to separate it from test logic.

2. Step 2: Apply to Hybrid framework

   Hybrid framework uses external files like Excel or CSV to manage test data for easy updates and reuse.

3. Final Answer:

   Store test data in external files like Excel or CSV. -> Option C

4. Quick Check:

   Test data external = Excel/CSV [OK]

Hint: Keep test data outside scripts for easy updates [OK]

Common Mistakes:

• Hardcoding data inside scripts reduces flexibility
• Mixing test data with Selenium code causes maintenance issues
• Using random data breaks test repeatability

3. Given the following snippet in a Hybrid framework:

String keyword = "click";
if (keyword.equals("click")) {
    driver.findElement(By.id("submitBtn")).click();
} else if (keyword.equals("input")) {
    driver.findElement(By.id("nameField")).sendKeys("John");
}

What will happen when this code runs?

medium

A. A runtime error will occur due to invalid locator.

B. The name field will receive the text "John".

C. No action will be performed.

D. The submit button will be clicked.

Solution

1. Step 1: Check the keyword value

   The variable keyword is set to "click".

2. Step 2: Follow the if condition

   Since keyword.equals("click") is true, the code clicks the element with id "submitBtn".

3. Final Answer:

   The submit button will be clicked. -> Option D

4. Quick Check:

   Keyword = "click" triggers click action [OK]

Hint: Match keyword to action to predict behavior [OK]

Common Mistakes:

• Confusing keyword values and actions
• Assuming input action runs when keyword is "click"
• Thinking locator is invalid without checking

4. In a Hybrid framework, the following code throws a NoSuchElementException. What is the likely cause?

driver.findElement(By.name("username")).sendKeys("admin");

medium

A. The sendKeys method is used incorrectly.

B. The locator By.name("username") does not match any element on the page.

C. The driver is not initialized before this line.

D. The element is disabled and cannot receive input.

Solution

1. Step 1: Understand NoSuchElementException meaning

   This exception means Selenium cannot find the element using the given locator.

2. Step 2: Analyze the locator usage

   If By.name("username") does not match any element on the current page, the exception occurs.

3. Final Answer:

   The locator By.name("username") does not match any element on the page. -> Option B

4. Quick Check:

   NoSuchElementException = locator not found [OK]

Hint: Check locator correctness when element not found error occurs [OK]

Common Mistakes:

• Blaming sendKeys syntax for element not found
• Ignoring driver initialization issues
• Assuming element disabled causes NoSuchElementException

5. You want to design a Hybrid framework that reads test steps from an Excel file and executes them using Selenium Java. Which approach best supports this design?

hard

A. Use a keyword-driven engine to interpret actions and a data-driven module to read test data from Excel.

B. Write all test steps directly in Java code without external files.

C. Use only data-driven testing by reading test data but hardcode actions in scripts.

D. Use random test data generation without keywords or external files.

Solution

1. Step 1: Understand Hybrid framework design goals

   Hybrid framework combines keyword-driven (for actions) and data-driven (for test data) approaches.

2. Step 2: Match design to Excel usage

   Reading test steps (keywords) and data from Excel fits keyword-driven engine plus data-driven module.

3. Final Answer:

   Use a keyword-driven engine to interpret actions and a data-driven module to read test data from Excel. -> Option A

4. Quick Check:

   Hybrid = keyword engine + data-driven Excel [OK]

Hint: Combine keyword engine with Excel data for Hybrid framework [OK]

Common Mistakes:

• Hardcoding all test steps reduces flexibility
• Ignoring keyword-driven part in Hybrid design
• Using random data breaks test consistency