Hybrid framework architecture in Selenium Java - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to initialize the WebDriver in a hybrid framework.

Selenium Java

WebDriver driver = new [1]();

Drag options to blanks, or click blank then click option'

AFirefoxOptions

BChromeDriver

CWebElement

DActions

Attempts:

3 left

💡 Hint

Common Mistakes

Using FirefoxOptions instead of FirefoxDriver

Confusing WebElement with WebDriver

Trying to instantiate Actions directly as WebDriver

In Selenium with Java, to start a browser session, you create an instance of a WebDriver implementation like ChromeDriver.

2fill in blank

medium

Complete the code to read test data from an Excel file in the hybrid framework.

Selenium Java

FileInputStream file = new FileInputStream("data.xlsx");
Workbook workbook = new [1](file);

Drag options to blanks, or click blank then click option'

ABufferedReader

BFileReader

CXSSFWorkbook

DSheet

Attempts:

3 left

💡 Hint

Common Mistakes

Using FileReader which is for text files

Using BufferedReader which reads text streams

Using Sheet which represents a sheet, not the workbook

XSSFWorkbook is used to read .xlsx Excel files in Apache POI library.

3fill in blank

hard

Fix the error in the assertion statement to verify the page title.

Selenium Java

Assert.[1](driver.getTitle(), "Expected Title");

Drag options to blanks, or click blank then click option'

AassertNotNull

BassertTrue

CassertNull

DassertEquals

Attempts:

3 left

💡 Hint

Common Mistakes

Using assertTrue with two arguments causes compilation error

Using assertNull or assertNotNull is incorrect for title comparison

assertEquals compares two values for equality, which is correct for verifying page title.

4fill in blank

hard

Fill both blanks to create a reusable method that clicks a button by locator in the hybrid framework.

Selenium Java

public void clickButton(By [1]) {
    driver.[2]([1]).click();
}

Drag options to blanks, or click blank then click option'

Alocator

BfindElement

Cclick

DBy

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'click' as parameter name

Using driver.click() which does not exist

Using 'By' as parameter name instead of a variable

The method parameter is named locator of type By, and driver.findElement(locator) finds the element to click.

5fill in blank

hard

Fill all three blanks to create a data-driven test method that reads username and password from Excel and logs in.

Selenium Java

String username = sheet.getRow([1]).getCell([2]).getStringCellValue();
String password = sheet.getRow([1]).getCell([3]).getStringCellValue();

Drag options to blanks, or click blank then click option'

A1

B0

D2

Attempts:

3 left

💡 Hint

Common Mistakes

Using row 0 which is header row

Mixing up cell indexes for username and password

Row 1 is usually the first data row (after header), cell 0 for username, cell 2 for password assuming columns: 0=username, 1=ignored, 2=password.

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