Why framework design enables scalability in Selenium Java - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to initialize the WebDriver for Chrome browser.

Selenium Java

WebDriver driver = new [1]();

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

AEdgeDriver

BFirefoxDriver

CSafariDriver

DChromeDriver

Attempts:

3 left

💡 Hint

Common Mistakes

Using FirefoxDriver when ChromeDriver is needed.

Forgetting to import the correct driver class.

The ChromeDriver class initializes the WebDriver for Chrome browser, which is commonly used in Selenium tests.

2fill in blank

medium

Complete the code to wait explicitly for an element to be visible.

Selenium Java

WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(10));
wait.[1](ExpectedConditions.visibilityOfElementLocated(By.id("submitBtn")));

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

Auntil

BwaitFor

Ccheck

Dfind

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent methods like waitFor or check.

Not using explicit waits causing flaky tests.

The until method waits until the given condition is true, here waiting for visibility of the element.

3fill in blank

hard

Fix the error in the test method annotation to enable test execution.

Selenium Java

@[1]
public void testLogin() {
    // test steps
}

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

ATest

Btest

CTestCase

DTestMethod

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase '@test' which is invalid.

Using '@TestCase' or '@TestMethod' which do not exist.

The correct JUnit 5 annotation to mark a test method is @Test with capital 'T'.

4fill in blank

hard

Fill both blanks to create a Page Object method that clicks a button by locator.

Selenium Java

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

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

ABy.id("submitBtn")

Bclick

Csubmit

DBy.name("submit")

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'submit' instead of 'click' for the action.

Using wrong locator types or missing parentheses.

The method findElement needs a locator like By.id("submitBtn"), and to click the button we use the click() method.

5fill in blank

hard

Fill all three blanks to create a test that asserts page title equals expected.

Selenium Java

String title = driver.[1]();
String expected = "Home Page";
assert[2](expected, title, "Title should match");
System.out.println("Page title is: " + [3]);

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

AgetTitle

BEquals

Ctitle

DassertEquals

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Equals' instead of 'assertEquals' for assertion.

Printing 'expected' instead of 'title'.

The getTitle() method gets the page title. The assertion method is assertEquals to compare expected and actual. Finally, print the title variable.

Practice

1. Why does using a test framework help when your test suite grows larger?

easy

A. It automatically writes new tests without human input.

B. It makes tests run slower but more accurately.

C. It organizes code to make adding new tests easier and faster.

D. It removes the need for any test maintenance.

Solution

1. Step 1: Understand framework purpose

   A test framework structures code and resources to manage tests efficiently.

2. Step 2: Connect framework to scalability

   Organized code allows easy addition and modification of tests as the suite grows.

3. Final Answer:

   It organizes code to make adding new tests easier and faster. -> Option C

4. Quick Check:

   Framework = organized, scalable tests [OK]

Hint: Frameworks help organize code for easy test growth [OK]

Common Mistakes:

• Thinking frameworks slow down tests
• Believing frameworks remove all maintenance
• Assuming frameworks auto-generate tests

2. Which Java code snippet best shows a reusable method in a Selenium test framework?

easy

A. public void login(String user, String pass) { driver.findElement(By.id("user")).sendKeys(user); driver.findElement(By.id("pass")).sendKeys(pass); driver.findElement(By.id("loginBtn")).click(); }

B. driver.findElement(By.id("user")).sendKeys("admin"); driver.findElement(By.id("pass")).sendKeys("1234"); driver.findElement(By.id("loginBtn")).click();

C. int x = 5; int y = 10; int sum = x + y;

D. System.out.println("Test started");

Solution

1. Step 1: Identify reusable method

   public void login(String user, String pass) { driver.findElement(By.id("user")).sendKeys(user); driver.findElement(By.id("pass")).sendKeys(pass); driver.findElement(By.id("loginBtn")).click(); } defines a method with parameters to reuse login steps with different data.

2. Step 2: Compare other options

   The other options are either hardcoded steps or unrelated code, not reusable methods.

3. Final Answer:

   Reusable login method with parameters -> Option A

4. Quick Check:

   Reusable method = method with parameters [OK]

Hint: Look for methods with parameters for reuse [OK]

Common Mistakes:

• Choosing hardcoded steps as reusable
• Confusing unrelated code as framework code
• Ignoring method parameters

3. Given this code snippet in a Selenium framework:

public void openPage() { driver.get("https://example.com"); }
public void login(String user, String pass) {
  driver.findElement(By.id("user")).sendKeys(user);
  driver.findElement(By.id("pass")).sendKeys(pass);
  driver.findElement(By.id("loginBtn")).click();
}
openPage();
login("admin", "1234");

What is the main benefit of this design when adding more tests?

medium

A. You can reuse openPage and login methods in many tests without rewriting code.

B. Tests will run slower because of method calls.

C. You must rewrite the login steps for each test.

D. The code will fail because methods are called outside a class.

Solution

1. Step 1: Analyze method usage

   openPage and login methods encapsulate common actions for reuse.

2. Step 2: Understand scalability impact

   Reusing methods avoids rewriting code, making it easier to add new tests.

3. Final Answer:

   Reuse methods to avoid rewriting code -> Option A

4. Quick Check:

   Reusable methods = easier test addition [OK]

Hint: Reusable methods save rewriting steps [OK]

Common Mistakes:

• Thinking method calls slow tests significantly
• Believing code must be rewritten each time
• Confusing syntax errors with design benefits

4. You have this Selenium test code snippet:

public void login(String user, String pass) {
  driver.findElement(By.id("username")).sendKeys(user);
  driver.findElement(By.id("password")).sendKeys(pass);
  driver.findElement(By.id("loginBtn")).click();
}
login("admin", "1234");

But the test fails because elements are not found. What is the likely fix to improve framework scalability?

medium

A. Remove the login method and write steps inline.

B. Use a centralized locator repository to manage element locators.

C. Hardcode element locators inside each test method.

D. Ignore element locators and rely on implicit waits only.

Solution

1. Step 1: Identify problem cause

   Element locators scattered cause maintenance issues and test failures.

2. Step 2: Apply framework design principle

   Centralizing locators in one place improves maintainability and scalability.

3. Final Answer:

   Use centralized locator repository -> Option B

4. Quick Check:

   Centralized locators = easier updates [OK]

Hint: Centralize locators to fix element not found errors [OK]

Common Mistakes:

• Hardcoding locators everywhere
• Removing reusable methods
• Relying only on waits without fixing locators

5. In a Selenium Java framework, you want to add a new feature test that requires login and navigation. Which design approach best supports scalability?

hard

A. Write separate tests for login and navigation without combining them.

B. Copy-paste login and navigation steps directly into the new test method.

C. Write all test steps inline without methods to keep it simple.

D. Create reusable methods for login and navigation, then call them in the new test.

Solution

1. Step 1: Understand scalability needs

   Scalable frameworks use reusable methods to avoid duplication and ease maintenance.

2. Step 2: Apply reusable methods to new feature

   Creating reusable login and navigation methods allows easy updates and test growth.

3. Final Answer:

   Create reusable methods and call them in tests -> Option D

4. Quick Check:

   Reusable methods enable scalable test design [OK]

Hint: Use reusable methods to add new features easily [OK]

Common Mistakes:

• Copy-pasting code causing maintenance issues
• Writing all steps inline making tests long
• Separating related steps into different tests unnecessarily