Test class consuming page objects in Selenium Java - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main purpose of a test class consuming page objects in Selenium?

The test class uses page objects to interact with web page elements in a clean and organized way, separating test logic from page details.

beginner

Why should locators be kept inside page objects rather than test classes?

Keeping locators inside page objects helps maintain code by isolating element details, so if the page changes, only the page object needs updating, not all tests.

beginner

How does a test class typically use a page object?

The test class creates an instance of the page object and calls its methods to perform actions or checks on the web page.

beginner

What is a benefit of using page objects in automated tests?

Page objects improve test readability and reduce code duplication by encapsulating page details and providing simple methods for tests.

intermediate

In Selenium with Java, what annotation is commonly used to initialize page objects?

The @FindBy annotation is used to locate elements, and PageFactory.initElements() initializes the page object fields.

What does a test class do with a page object?

A Calls methods on the page object to interact with the page

B Defines locators inside the test class

C Directly manipulates browser without page objects

D Writes HTML code for the page

Test classes use page objects by calling their methods to perform actions or checks on the web page.

Where should element locators be stored for best practice?

A Hardcoded in test methods

B Inside the test class

C In a separate XML file

D Inside the page object

Locators belong inside page objects to keep tests clean and maintainable.

Which Selenium feature helps initialize page objects in Java?

A WebDriverWait

B Actions class

C PageFactory.initElements()

D JavascriptExecutor

PageFactory.initElements() initializes the elements annotated with @FindBy in page objects.

What is a key advantage of using page objects?

A Better separation of test logic and page details

B Faster browser loading

C No need for assertions

D Tests run without WebDriver

Page objects separate test logic from page details, making tests easier to read and maintain.

In a test class, how do you typically start using a page object?

A By calling WebDriver directly

B By creating an instance of the page object class

C By writing locators in the test method

D By importing HTML files

Test classes create instances of page objects to use their methods for interacting with the page.

Explain how a test class uses a page object to perform a login test.

Think about how the test class talks to the page object methods instead of directly using locators.

Describe the benefits of using page objects in Selenium tests.

Consider how page objects help when the web page changes or when writing many tests.

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