Hybrid framework architecture in Selenium Java - Test Execution Trace

Test Overview

This test automates login functionality using a hybrid framework combining data-driven and keyword-driven approaches. It verifies successful login by checking the presence of a logout button.

Test Code - TestNG with Selenium WebDriver

Selenium Java

import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import org.openqa.selenium.chrome.ChromeDriver;
import org.testng.Assert;
import org.testng.annotations.AfterClass;
import org.testng.annotations.BeforeClass;
import org.testng.annotations.DataProvider;
import org.testng.annotations.Test;

public class HybridLoginTest {
    WebDriver driver;

    @BeforeClass
    public void setup() {
        System.setProperty("webdriver.chrome.driver", "path/to/chromedriver");
        driver = new ChromeDriver();
        driver.manage().window().maximize();
    }

    @DataProvider(name = "loginData")
    public Object[][] loginData() {
        return new Object[][] {
            {"user1", "pass1"},
            {"user2", "pass2"}
        };
    }

    @Test(dataProvider = "loginData")
    public void testLogin(String username, String password) {
        driver.get("https://example.com/login");

        // Keyword-driven steps
        performAction("enterText", "id=username", username);
        performAction("enterText", "id=password", password);
        performAction("click", "id=loginBtn", null);

        // Assertion
        WebElement logoutBtn = driver.findElement(By.id("logoutBtn"));
        Assert.assertTrue(logoutBtn.isDisplayed(), "Logout button should be visible after login");
    }

    public void performAction(String action, String locator, String value) {
        By byLocator = getBy(locator);
        WebElement element = driver.findElement(byLocator);
        switch (action) {
            case "enterText":
                element.sendKeys(value);
                break;
            case "click":
                element.click();
                break;
            default:
                throw new IllegalArgumentException("Invalid action: " + action);
        }
    }

    public By getBy(String locator) {
        String[] parts = locator.split("=", 2);
        switch (parts[0]) {
            case "id":
                return By.id(parts[1]);
            case "name":
                return By.name(parts[1]);
            case "xpath":
                return By.xpath(parts[1]);
            default:
                throw new IllegalArgumentException("Invalid locator type: " + parts[0]);
        }
    }

    @AfterClass
    public void teardown() {
        if (driver != null) {
            driver.quit();
        }
    }
}

Execution Trace - 8 Steps

Step	Action	System State	Assertion	Result
1	Test setup: ChromeDriver initialized and browser window maximized	Chrome browser opened, ready for navigation	—	PASS
2	Navigate to https://example.com/login	Login page loaded with username, password fields and login button	Page URL is correct	PASS
3	Find username field by id and enter 'user1'	Username input filled with 'user1'	Username field contains 'user1'	PASS
4	Find password field by id and enter 'pass1'	Password input filled with 'pass1'	Password field contains 'pass1'	PASS
5	Find login button by id and click	Login form submitted, page loading user dashboard	—	PASS
6	Find logout button by id to verify login success	Logout button visible on dashboard page	Logout button is displayed	PASS
7	Repeat steps 2-6 for second data set: username 'user2', password 'pass2'	Second login attempt successful, logout button visible	Logout button is displayed	PASS
8	Test teardown: Close browser and quit driver	Browser closed, WebDriver session ended	—	PASS

Failure Scenario

Failing Condition: Logout button not found after login attempt

Execution Trace Quiz - 3 Questions

What does the test verify after clicking the login button?

A That the logout button is visible on the page

B That the login button is disabled

C That the username field is cleared

D That an error message appears

Key Result

Combining data-driven and keyword-driven techniques in a hybrid framework improves test flexibility and reusability by separating test data from test steps.

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