Why Test class consuming page objects in Selenium Java? - Purpose & Use Cases

The Big Idea

What if you could fix one place and save hours of test updates?

The Scenario

Imagine testing a website by writing all the code to find buttons, fields, and links directly inside your test methods. Every time the page changes, you must hunt through your tests to fix locators.

The Problem

This manual way is slow and confusing. Tests become long and messy. If the page layout changes, many tests break and need fixing. It's easy to make mistakes and hard to understand what each test does.

The Solution

Using page objects means creating separate classes that represent pages. These classes hold all locators and actions. Tests then just call these clean methods. When the page changes, only the page object class needs updating.

Before vs After

✗ Before

driver.findElement(By.id("loginBtn")).click();
String title = driver.getTitle();
assertEquals("Welcome", title);

✓ After

LoginPage login = new LoginPage(driver);
login.clickLoginButton();
assertEquals("Welcome", login.getTitle());

What It Enables

This approach makes tests easier to read, maintain, and update, saving time and reducing errors.

Real Life Example

When a website changes its login button ID, you update it once in the LoginPage class, and all tests using it continue working without changes.

Key Takeaways

Manual test code mixes page details and test logic, causing confusion.

Page objects separate page details from tests, making maintenance simpler.

Tests become cleaner, faster to fix, and more reliable.

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