Dependency between tests in Selenium Java - Test Execution Trace

Test Overview

This test suite demonstrates dependency between tests using Selenium in Java. The first test logs in a user, and the second test depends on the login test to verify the user profile page.

Test Code - JUnit 5 with Selenium WebDriver

Selenium Java

import org.junit.jupiter.api.*;
import org.openqa.selenium.*;
import org.openqa.selenium.chrome.ChromeDriver;
import static org.junit.jupiter.api.Assertions.*;

@TestMethodOrder(MethodOrderer.OrderAnnotation.class)
public class DependencyTest {
    static WebDriver driver;

    @BeforeAll
    public static void setup() {
        driver = new ChromeDriver();
        driver.manage().window().maximize();
    }

    @Test
    @Order(1)
    public void testLogin() {
        driver.get("https://example.com/login");
        WebElement username = driver.findElement(By.id("username"));
        WebElement password = driver.findElement(By.id("password"));
        WebElement loginButton = driver.findElement(By.id("loginBtn"));

        username.sendKeys("testuser");
        password.sendKeys("password123");
        loginButton.click();

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

    @Test
    @Order(2)
    public void testUserProfile() {
        // This test depends on successful login
        driver.get("https://example.com/profile");
        WebElement profileHeader = driver.findElement(By.tagName("h1"));
        assertEquals("User Profile", profileHeader.getText(), "Profile page header should be 'User Profile'");
    }

    @AfterAll
    public static void teardown() {
        if (driver != null) {
            driver.quit();
        }
    }
}

Execution Trace - 8 Steps

Step	Action	System State	Assertion	Result
1	Test suite setup: Launch Chrome browser and maximize window	Chrome browser opened, blank page	—	PASS
2	Navigate to login page at https://example.com/login	Login page loaded with username, password fields and login button	—	PASS
3	Find username, password input fields and login button	Elements located by id: username, password, loginBtn	—	PASS
4	Enter username 'testuser' and password 'password123', then click login button	Login form submitted	—	PASS
5	Find welcome message element by id 'welcomeMsg'	Welcome message displayed on page	Verify welcome message is visible	PASS
6	Navigate to user profile page at https://example.com/profile	Profile page loaded with header	—	PASS
7	Find profile page header element by tag name 'h1'	Header element found with text 'User Profile'	Verify header text equals 'User Profile'	PASS
8	Test suite teardown: Close browser	Browser closed	—	PASS

Failure Scenario

Failing Condition: Login test fails causing user not to be logged in before profile test runs

Execution Trace Quiz - 3 Questions

What ensures that the user profile test runs only after the login test?

A The profile test calls the login test method explicitly

B The use of WebDriverWait in the profile test

C The @Order annotation specifying test execution order

D JUnit automatically runs tests in alphabetical order

Key Result

Use test ordering annotations to manage dependencies between tests, ensuring prerequisite tests run first to set up required state.

Practice

1. What is the main purpose of using dependsOnMethods in Selenium Java tests?

easy

A. To skip tests that have no assertions

B. To run all tests in parallel regardless of order

C. To automatically retry failed tests

D. To make one test run only after another test has passed

Solution

1. Step 1: Understand test dependencies

   The dependsOnMethods attribute is used to specify that a test should run only after another test method has successfully completed.

2. Step 2: Recognize the effect on test execution order

   This ensures that dependent tests do not run if the test they depend on fails, maintaining logical test flow.

3. Final Answer:

   To make one test run only after another test has passed -> Option D

4. Quick Check:

   dependsOnMethods controls test order and dependency [OK]

Hint: dependsOnMethods links tests to run in sequence [OK]

Common Mistakes:

• Thinking dependsOnMethods runs tests in parallel
• Assuming it retries failed tests automatically
• Believing it skips tests without assertions

2. Which of the following is the correct syntax to make testB depend on testA in TestNG?

easy

A. @Test(dependsOnMethods = testA) public void testB() {}

B. @Test(dependsOnMethods = {"testA"}) public void testB() {}

C. @Test(dependsOn = "testA") public void testB() {}

D. @Test(dependOn = "testA") public void testB() {}

Solution

1. Step 1: Recall TestNG annotation syntax

   The correct attribute name is dependsOnMethods and it expects an array of method names as strings.

2. Step 2: Check the syntax correctness

   @Test(dependsOnMethods = {"testA"}) public void testB() {} correctly uses @Test(dependsOnMethods = {"testA"}) with the method name in quotes inside braces.

3. Final Answer:

   @Test(dependsOnMethods = {"testA"}) public void testB() {} -> Option B

4. Quick Check:

   dependsOnMethods requires string array syntax [OK]

Hint: Use dependsOnMethods with braces and quotes [OK]

Common Mistakes:

• Using dependsOn instead of dependsOnMethods
• Omitting quotes around method name
• Not using braces for the array

3. Given the following TestNG code:

@Test
public void login() { Assert.assertTrue(false); }

@Test(dependsOnMethods = {"login"})
public void dashboard() { System.out.println("Dashboard loaded"); }

What will happen when these tests run?

medium

A. login fails, dashboard is skipped

B. login fails, dashboard runs and prints message

C. Both login and dashboard run and pass

D. login passes, dashboard is skipped

Solution

1. Step 1: Analyze login test result

   The login test asserts false, so it will fail.

2. Step 2: Understand effect on dependent test

   The dashboard test depends on login. Since login failed, dashboard will be skipped and not run.

3. Final Answer:

   login fails, dashboard is skipped -> Option A

4. Quick Check:

   Dependent tests skip if dependency fails [OK]

Hint: Failed dependency causes dependent test to skip [OK]

Common Mistakes:

• Assuming dependent test runs despite failure
• Thinking both tests pass
• Confusing skip with fail

4. Identify the error in this TestNG test dependency code:

@Test(dependsOnMethods = "setup")
public void testFeature() {}

@Test
public void setup() {}

medium

A. setup method must be private

B. testFeature should not depend on setup

C. dependsOnMethods should be an array of strings, not a single string

D. setup method must have parameters

Solution

1. Step 1: Check dependsOnMethods syntax

   The attribute dependsOnMethods requires an array of method names, even if only one method is listed.

2. Step 2: Identify the syntax mistake

   Here, dependsOnMethods = "setup" is a single string, missing braces to make it an array.

3. Final Answer:

   dependsOnMethods should be an array of strings, not a single string -> Option C

4. Quick Check:

   dependsOnMethods needs braces for method names [OK]

Hint: Always use braces {} for dependsOnMethods even if one method [OK]

Common Mistakes:

• Using single string instead of string array
• Making dependent method private
• Adding parameters to setup method unnecessarily

5. You have three tests: init(), login(), and purchase(). login() depends on init(), and purchase() depends on login(). If init() fails, what happens when you run all tests together?

hard

A. init fails, login and purchase are skipped

B. init fails, login runs but purchase is skipped

C. init fails, login and purchase run anyway

D. init fails, only purchase runs

Solution

1. Step 1: Understand the dependency chain

   login depends on init, and purchase depends on login, forming a chain: init -> login -> purchase.

2. Step 2: Analyze failure impact

   If init fails, login will be skipped because it depends on init. Since login is skipped, purchase will also be skipped because it depends on login.

3. Final Answer:

   init fails, login and purchase are skipped -> Option A

4. Quick Check:

   Failure cascades down dependent tests [OK]

Hint: Failure in first test skips all dependent tests down the chain [OK]

Common Mistakes:

• Assuming dependent tests run despite failure
• Thinking only immediate dependent test skips
• Believing tests run independently