Test class consuming page objects in Selenium Java - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare the WebDriver variable in the test class.

Selenium Java

private WebDriver [1];

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

Adriver

Bbrowser

CwebDriver

DpageDriver

Attempts:

3 left

💡 Hint

Common Mistakes

Using uncommon or unclear variable names like 'pageDriver' which can confuse readers.

The WebDriver variable is commonly named driver in Selenium test classes for clarity and convention.

2fill in blank

medium

Complete the code to initialize the page object in the test setup method.

Selenium Java

loginPage = new LoginPage([1]);

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

Anull

BpageDriver

Cdriver

Dthis

Attempts:

3 left

💡 Hint

Common Mistakes

Passing null or unrelated variables instead of the WebDriver instance.

The page object constructor requires the WebDriver instance, which is driver in the test class.

3fill in blank

hard

Fix the error in the test method to call the login method from the page object.

Selenium Java

loginPage.[1]("user", "pass");

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

Alogin

BsignIn

Csubmit

Dauthenticate

Attempts:

3 left

💡 Hint

Common Mistakes

Using method names that do not exist in the page object like 'signIn' or 'authenticate'.

The page object method to perform login is named login, so calling loginPage.login() is correct.

4fill in blank

hard

Fill both blanks to assert the page title after login.

Selenium Java

assertEquals([1], driver.[2]());

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

A"Dashboard"

BgetTitle

CgetCurrentUrl

D"Login Page"

Attempts:

3 left

💡 Hint

Common Mistakes

Using getCurrentUrl() instead of getTitle() to check the page title.

After login, the expected page title is "Dashboard" and the WebDriver method to get the title is getTitle().

5fill in blank

hard

Fill all three blanks to properly close the browser after tests.

Selenium Java

if (driver != null) {
    driver.[1]();
    driver = [2];
    loginPage = [3];
}

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

Aquit

Bnull

Dclose

Attempts:

3 left

💡 Hint

Common Mistakes

Using driver.close() which only closes one window, not the entire browser session.

Not setting variables to null after quitting.

To close the browser, call driver.quit(). Then set driver and loginPage to null to clean up references.

Practice

1. What is the main purpose of a test class when it consumes page objects in Selenium Java?

easy

A. To locate web elements directly using Selenium locators

B. To manage browser driver setup and teardown only

C. To define the structure of the web page elements

D. To perform test steps and assertions using methods from page objects

Solution

1. Step 1: Understand roles of test class and page objects

   Page objects encapsulate web element locators and actions. Test classes use these to perform tests.

2. Step 2: Identify test class responsibility

   Test classes call page object methods to execute test steps and verify results with assertions.

3. Final Answer:

   To perform test steps and assertions using methods from page objects -> Option D

4. Quick Check:

   Test class runs tests using page objects [OK]

Hint: Test classes call page object methods to run tests [OK]

Common Mistakes:

• Trying to locate elements directly in test class
• Mixing page object code with test logic
• Using test class only for driver setup

2. Which of the following is the correct way to instantiate a page object in a Selenium Java test class?

easy

A. LoginPage login = new LoginPage(driver);

B. LoginPage login = LoginPage();

C. LoginPage login = new LoginPage();

D. LoginPage login = driver.get(LoginPage.class);

Solution

1. Step 1: Recall page object constructor usage

   Page objects usually require WebDriver passed to constructor for element initialization.

2. Step 2: Check each option for correct syntax

   LoginPage login = new LoginPage(driver); correctly uses 'new' with driver argument. Others miss driver or use invalid syntax.

3. Final Answer:

   LoginPage login = new LoginPage(driver); -> Option A

4. Quick Check:

   Use 'new' with driver parameter [OK]

Hint: Always pass driver to page object constructor [OK]

Common Mistakes:

• Forgetting to pass driver to constructor
• Using constructor without 'new' keyword
• Trying to get page object from driver directly

3. Given the following test class snippet, what will be the output if the login fails?

LoginPage login = new LoginPage(driver);
boolean result = login.login("wrongUser", "wrongPass");
System.out.println(result ? "Login Successful" : "Login Failed");

Assuming login() returns true on success and false on failure.

medium

A. Login Failed

B. Compilation error

C. Login Successful

D. Runtime exception

Solution

1. Step 1: Understand login method behavior

   login() returns true if credentials are correct, false otherwise.

2. Step 2: Analyze given credentials and output

   Credentials are wrong, so login() returns false, printing "Login Failed".

3. Final Answer:

   Login Failed -> Option A

4. Quick Check:

   False login returns "Login Failed" [OK]

Hint: Check boolean return to decide output [OK]

Common Mistakes:

• Assuming login returns exception on failure
• Confusing true/false return values
• Ignoring ternary operator logic

4. Identify the error in this test class code snippet that uses a page object:

public class LoginTest {
  WebDriver driver;
  LoginPage loginPage;

  @Before
  public void setup() {
    driver = new ChromeDriver();
    loginPage = new LoginPage();
  }

  @Test
  public void testLogin() {
    loginPage.login("user", "pass");
  }
}

medium

A. Test method missing assertion

B. WebDriver is not initialized before use

C. LoginPage constructor is called without passing driver

D. Missing @After method to quit driver

Solution

1. Step 1: Check page object instantiation

   LoginPage requires driver in constructor, but called without arguments here.

2. Step 2: Confirm driver initialization

   Driver is initialized correctly before page object creation, so no issue there.

3. Final Answer:

   LoginPage constructor is called without passing driver -> Option C

4. Quick Check:

   Page object needs driver in constructor [OK]

Hint: Always pass driver when creating page objects [OK]

Common Mistakes:

• Forgetting driver parameter in page object constructor
• Assuming driver auto-initializes in page object
• Ignoring missing assertions (not error here)

5. You want to write a test class that uses two page objects: HomePage and ProfilePage. You want to test the flow: login, navigate to profile, update info, and verify success message. Which approach best follows the test class consuming page objects pattern?

hard

A. Write all element locators and actions inside the test class without page objects

B. Instantiate both page objects with driver, call login on HomePage, then call updateProfile on ProfilePage, finally assert success message from ProfilePage

C. Create one page object combining HomePage and ProfilePage methods, then test all steps there

D. Use driver directly in test class to click and send keys for all steps

Solution

1. Step 1: Understand separation of concerns

   Page objects encapsulate page details; test class uses them to perform test steps and assertions.

2. Step 2: Evaluate options for best practice

   Instantiate both page objects with driver, call login on HomePage, then call updateProfile on ProfilePage, finally assert success message from ProfilePage correctly uses separate page objects and test class calls their methods in sequence.

3. Final Answer:

   Instantiate both page objects with driver, call login on HomePage, then call updateProfile on ProfilePage, finally assert success message from ProfilePage -> Option B

4. Quick Check:

   Test class calls page objects methods in flow [OK]

Hint: Use separate page objects, call their methods in test class [OK]

Common Mistakes:

• Putting all locators and actions in test class
• Combining unrelated page objects into one
• Using driver directly instead of page objects