Dependency between tests in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why avoid dependencies between tests?

In Selenium test automation, why is it important to avoid dependencies between tests?

A Because dependent tests can cause cascading failures making debugging harder.

B Because dependent tests reduce the need for setup and teardown methods.

C Because dependent tests run faster and improve performance.

D Because dependent tests always pass regardless of application state.

💡 Hint

Think about what happens if one test fails and others rely on it.

Tests that depend on each other can cause multiple failures if one test fails, making it difficult to find the root cause. Independent tests improve reliability and ease debugging.

❓ Predict Output

intermediate

Test execution order with dependencies

Given the following Selenium Java test methods with TestNG annotations, what will be the output when running the test suite?

Selenium Java

import org.testng.annotations.Test;

public class SampleTest {

    @Test(dependsOnMethods = {"testLogin"})
    public void testDashboard() {
        System.out.println("Dashboard test executed");
    }

    @Test
    public void testLogin() {
        System.out.println("Login test executed");
    }

    @Test(dependsOnMethods = {"testDashboard"})
    public void testSettings() {
        System.out.println("Settings test executed");
    }
}

A

Settings test executed
Dashboard test executed
Login test executed

B

Dashboard test executed
Login test executed
Settings test executed

C

Login test executed
Settings test executed
Dashboard test executed

D

Login test executed
Dashboard test executed
Settings test executed

💡 Hint

Tests run after their dependencies have run successfully.

testLogin runs first because others depend on it. Then testDashboard runs, followed by testSettings which depends on testDashboard.

❓ assertion

advanced

Assertion failure impact on dependent tests

Consider these TestNG tests where testLogin fails due to an assertion error. What happens to testDashboard which depends on testLogin?

Selenium Java

import org.testng.Assert;
import org.testng.annotations.Test;

public class LoginTests {

    @Test
    public void testLogin() {
        Assert.assertTrue(false, "Login failed");
    }

    @Test(dependsOnMethods = {"testLogin"})
    public void testDashboard() {
        System.out.println("Dashboard test executed");
    }
}

A testDashboard runs before testLogin.

B testDashboard is skipped because testLogin failed.

C testDashboard runs and fails due to testLogin failure.

D testDashboard runs and passes despite testLogin failure.

💡 Hint

Think about how TestNG handles dependencies when a test fails.

If a test that others depend on fails, TestNG skips the dependent tests to avoid false failures.

🔧 Debug

advanced

Fix the flaky test caused by dependency

These two Selenium tests depend on each other causing flaky failures. Identify the main problem and select the best fix.

Selenium Java

import org.testng.annotations.Test;

public class FlakyTests {

    @Test(dependsOnMethods = {"testAddItem"})
    public void testCheckout() {
        System.out.println("Checkout test executed");
    }

    @Test(dependsOnMethods = {"testCheckout"})
    public void testAddItem() {
        System.out.println("Add item test executed");
    }
}

A Keep dependencies as is; TestNG will handle circular dependencies automatically.

B Add a third test that both depend on to fix the order.

C Remove the dependency from testAddItem on testCheckout to break the circular dependency.

D Change both tests to run in parallel to avoid dependency issues.

💡 Hint

Look for circular dependencies and how they affect test execution.

There is a circular dependency between testAddItem and testCheckout causing flaky runs. Removing one dependency breaks the cycle and stabilizes tests.

❓ framework

expert

Best practice for managing test dependencies in Selenium with TestNG

Which approach is best to manage dependencies between Selenium tests in TestNG to ensure reliable and maintainable test suites?

A Design tests to be independent and use setup methods to prepare required state instead of relying on other tests.

B Use <code>dependsOnMethods</code> extensively to control test order and share state between tests.

C Combine multiple test scenarios into one large test to avoid dependencies.

D Disable tests that fail due to dependencies and rerun them manually later.

💡 Hint

Think about test reliability and ease of maintenance.

Independent tests with proper setup and teardown are more reliable and easier to maintain than tests relying on dependencies which cause fragility.