Why patterns improve test quality in JUnit - Test Execution Impact

Test Overview

This test checks that using a test pattern (Page Object Model) helps keep tests clear and reliable by separating page details from test logic.

Test Code - JUnit

JUnit

import org.junit.jupiter.api.Test;
import static org.junit.jupiter.api.Assertions.*;
import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import org.openqa.selenium.chrome.ChromeDriver;

class LoginPage {
    private WebDriver driver;
    private By usernameField = By.id("username");
    private By passwordField = By.id("password");
    private By loginButton = By.id("loginBtn");

    public LoginPage(WebDriver driver) {
        this.driver = driver;
    }

    public void enterUsername(String username) {
        driver.findElement(usernameField).sendKeys(username);
    }

    public void enterPassword(String password) {
        driver.findElement(passwordField).sendKeys(password);
    }

    public void clickLogin() {
        driver.findElement(loginButton).click();
    }
}

public class LoginTest {

    @Test
    void testValidLogin() {
        WebDriver driver = new ChromeDriver();
        driver.get("https://example.com/login");

        LoginPage loginPage = new LoginPage(driver);
        loginPage.enterUsername("user1");
        loginPage.enterPassword("pass123");
        loginPage.clickLogin();

        WebElement welcomeMessage = driver.findElement(By.id("welcomeMsg"));
        assertTrue(welcomeMessage.isDisplayed(), "Welcome message should be visible after login");

        driver.quit();
    }
}

Execution Trace - 10 Steps

Step	Action	System State	Assertion	Result
1	Test starts	JUnit test runner initializes	—	PASS
2	Browser opens ChromeDriver	Chrome browser window opens at blank page	—	PASS
3	Navigates to https://example.com/login	Login page loads with username, password fields and login button	—	PASS
4	Creates LoginPage object with driver	Page object ready to interact with login page elements	—	PASS
5	Calls enterUsername("user1")	Username field found and filled with 'user1'	—	PASS
6	Calls enterPassword("pass123")	Password field found and filled with 'pass123'	—	PASS
7	Calls clickLogin()	Login button found and clicked, page processes login	—	PASS
8	Finds element with id 'welcomeMsg'	Welcome message element is present on page	Check if welcome message is displayed	PASS
9	Assert welcome message is visible	Welcome message visible to user	assertTrue(welcomeMessage.isDisplayed())	PASS
10	Closes browser and ends test	Browser closed, test finished	—	PASS

Failure Scenario

Failing Condition: If the login button locator changes and is not updated in LoginPage class

Execution Trace Quiz - 3 Questions

Why does using the LoginPage class improve test quality?

A It automatically fixes broken locators

B It makes the test run faster by skipping steps

C It separates page details from test logic making tests easier to read and maintain

D It removes the need for assertions

Key Result

Using test patterns like the Page Object Model keeps tests clean and easier to update when page details change, improving test quality and maintainability.

Practice

1. Why do test patterns improve the quality of JUnit tests?

easy

A. They remove the need for assertions

B. They increase the runtime of tests significantly

C. They make tests easier to read and maintain

D. They automatically fix bugs in the code

Solution

1. Step 1: Understand the purpose of test patterns

   Test patterns organize test code to be clear and structured.

2. Step 2: Connect patterns to test quality

   Clear and maintainable tests help developers understand and update tests easily, improving quality.

3. Final Answer:

   They make tests easier to read and maintain -> Option C

4. Quick Check:

   Patterns improve readability = A [OK]

Hint: Patterns improve readability and maintenance [OK]

Common Mistakes:

• Thinking patterns increase test runtime
• Believing patterns remove assertions
• Assuming patterns fix bugs automatically

2. Which JUnit annotation is commonly used to apply the 'Arrange-Act-Assert' pattern in tests?

easy

A. @BeforeEach

B. @Test

C. @AfterAll

D. @Disabled

Solution

1. Step 1: Identify the annotation that marks test methods

   @Test marks the method where Arrange-Act-Assert steps happen.

2. Step 2: Understand other annotations' roles

   @BeforeEach runs setup before each test, @AfterAll runs after all tests, @Disabled skips tests.

3. Final Answer:

   @Test -> Option B

4. Quick Check:

   Test method annotation = D [OK]

Hint: Use @Test for main test steps [OK]

Common Mistakes:

• Confusing @BeforeEach with test method annotation
• Using @AfterAll for test logic
• Thinking @Disabled runs tests

3. Consider this JUnit test snippet using the 'Arrange-Act-Assert' pattern:

int result = calculator.add(2, 3);
assertEquals(5, result);

What will happen if the method add returns 4 instead of 5?

medium

A. The test will fail with an assertion error

B. The test will pass successfully

C. The test will throw a compilation error

D. The test will be skipped automatically

Solution

1. Step 1: Understand the assertion

   assertEquals(5, result) expects result to be 5.

2. Step 2: Analyze the returned value

   If add returns 4, the assertion fails because 4 != 5.

3. Final Answer:

   The test will fail with an assertion error -> Option A

4. Quick Check:

   Wrong result causes assertion failure = A [OK]

Hint: Assertion expects exact value; mismatch fails test [OK]

Common Mistakes:

• Assuming test passes with wrong result
• Thinking compilation error occurs
• Believing test skips on failure

4. This JUnit test uses a pattern but has an error:

@Test
public void testDivide() {
  int result = calculator.divide(10, 0);
  assertEquals(0, result);
}

What is the main problem here?

medium

A. Missing @BeforeEach annotation causes setup failure

B. assertEquals expects wrong value, test will pass incorrectly

C. Test method name is invalid

D. Division by zero causes an exception, test will error

Solution

1. Step 1: Identify the operation causing error

   Dividing by zero throws an exception in Java.

2. Step 2: Understand test behavior on exception

   Test will error because exception is not caught or expected.

3. Final Answer:

   Division by zero causes an exception, test will error -> Option D

4. Quick Check:

   Divide by zero throws exception = C [OK]

Hint: Division by zero throws error, not returns zero [OK]

Common Mistakes:

• Assuming test passes with zero result
• Thinking missing @BeforeEach causes error here
• Believing method name affects test execution

5. You want to improve your JUnit tests by applying the 'Arrange-Act-Assert' pattern consistently. Which approach best improves test quality?

hard

A. Separate setup, execution, and verification clearly in each @Test method

B. Write all test logic inside @BeforeEach methods

C. Use multiple assertions in @AfterAll methods

D. Avoid using assertions to speed up tests

Solution

1. Step 1: Understand the 'Arrange-Act-Assert' pattern

   This pattern divides tests into setup (Arrange), action (Act), and checks (Assert) within the test method.

2. Step 2: Identify best practice for test quality

   Keeping these steps clear inside each @Test method improves readability and debugging.

3. Final Answer:

   Separate setup, execution, and verification clearly in each @Test method -> Option A

4. Quick Check:

   Clear step separation in tests = B [OK]

Hint: Keep Arrange, Act, Assert steps clear inside @Test [OK]

Common Mistakes:

• Putting all logic in @BeforeEach
• Using assertions outside test methods
• Skipping assertions to save time