Dependency between tests in Selenium Java - Framework Patterns

Framework Mode - Dependency between tests

Folder Structure

src/
└── test/
    └── java/
        └── com/
            └── example/
                ├── pages/
                │   └── LoginPage.java
                ├── tests/
                │   ├── LoginTests.java
                │   └── DashboardTests.java
                ├── utils/
                │   ├── WebDriverFactory.java
                │   └── TestDataLoader.java
                └── config/
                    └── TestConfig.java

Test Framework Layers

• Driver Layer: Manages WebDriver instances (e.g., WebDriverFactory.java).
• Page Objects: Encapsulate page elements and actions (e.g., LoginPage.java).
• Test Layer: Contains test classes with test methods (e.g., LoginTests.java).
• Utilities: Helper classes for data loading, waits, logging (e.g., TestDataLoader.java).
• Configuration: Holds environment and test settings (e.g., TestConfig.java).

Dependency between tests: Use TestNG's dependsOnMethods or dependsOnGroups annotations to specify test order and dependencies.

Configuration Patterns

• Environment Settings: Use TestConfig.java or property files to define URLs, credentials, and browser types.
• Browser Selection: Pass browser type as a parameter or system property to WebDriverFactory.
• Credentials: Store securely in environment variables or encrypted files, accessed via config classes.
• Test Dependencies: Define dependencies in TestNG XML or via annotations in test classes.

Test Reporting and CI/CD Integration

• Use TestNG built-in reports for pass/fail status and detailed logs.
• Integrate with Allure or ExtentReports for enhanced visual reports.
• Configure CI tools (Jenkins, GitHub Actions) to run tests and publish reports automatically.
• Fail dependent tests if their prerequisite tests fail, ensuring clear failure cause.

Best Practices for Dependency Between Tests

1. Minimize dependencies: Keep tests independent when possible to avoid cascading failures.
2. Use TestNG annotations: Use @Test(dependsOnMethods = {"methodName"}) to declare dependencies clearly.
3. Clear naming: Name tests to reflect their purpose and dependency order.
4. Fail fast: If a prerequisite test fails, skip dependent tests to save time and avoid misleading results.
5. Separate setup: Use @BeforeClass or @BeforeMethod for common setup instead of test dependencies when possible.

Self Check

Where in this folder structure would you add a new test method that must run only after a successful login test?

Key Result

Use TestNG's dependsOnMethods annotation to manage test dependencies clearly and reliably.

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