Why TestNG structures test execution in Selenium Java - Framework Benefits

Framework Mode - Why TestNG structures test execution

Folder Structure

selenium-testng-project/
├── src/
│   ├── main/
│   │   └── java/
│   │       └── com/example/app/
│   │           └── pages/
│   │               └── LoginPage.java
│   └── test/
│       └── java/
│           └── com/example/tests/
│               ├── LoginTest.java
│               └── BaseTest.java
├── testng.xml
├── pom.xml
└── README.md

Test Framework Layers

• Test Layer: Contains test classes like LoginTest.java where TestNG annotations (@Test, @BeforeMethod) define test methods and execution order.
• Page Object Layer: Classes representing UI pages (e.g., LoginPage.java) encapsulate web element locators and actions.
• Base Test Layer: BaseTest.java sets up WebDriver, configures browser, and manages test lifecycle with TestNG annotations.
• Configuration Layer: testng.xml controls test suites, groups, parallel execution, and test order.
• Utilities Layer: Helper classes for waits, logging, and reusable methods.

Configuration Patterns

testng.xml is the main configuration file. It defines:

• Which test classes or methods to run.
• Test groups for selective execution.
• Parallel execution settings (methods, classes, tests).
• Test dependencies and execution order.

Environment variables and browser settings are usually managed in BaseTest.java or external property files loaded during setup.

Test Reporting and CI/CD Integration

• TestNG generates default HTML and XML reports after test execution.
• Reports show passed, failed, skipped tests with stack traces.
• Reports can be integrated with CI/CD tools like Jenkins to visualize test results.
• TestNG listeners (e.g., ITestListener) can be implemented to customize reporting or trigger actions on test events.

Best Practices

• Use testng.xml to control test execution order and grouping instead of hardcoding in tests.
• Keep test methods independent; use TestNG dependencies only when necessary.
• Use annotations like @BeforeMethod and @AfterMethod for setup and cleanup to avoid flaky tests.
• Leverage parallel execution in testng.xml to speed up test runs but ensure thread safety.
• Implement Page Object Model to separate test logic from UI details.

Self Check

Where in this framework structure would you add a new test class for verifying the user registration page?

Key Result

TestNG structures test execution using annotations and XML configuration to control order, grouping, and parallelism.

Practice

1. Why does TestNG structure test execution using features like priority and dependsOnMethods?

easy

A. To make tests run randomly without any order

B. To control the order and dependencies between tests for smoother runs

C. To skip all tests automatically

D. To run tests only once without retries

Solution

1. Step 1: Understand TestNG test execution control

   TestNG uses features like priority and dependsOnMethods to manage the order and dependencies of tests.

2. Step 2: Recognize the benefit of structured execution

   This control helps tests run smoothly and find problems faster by running in a logical order.

3. Final Answer:

   To control the order and dependencies between tests for smoother runs -> Option B

4. Quick Check:

   TestNG structures execution = Control order & dependencies [OK]

Hint: TestNG orders tests to avoid chaos and errors [OK]

Common Mistakes:

• Thinking TestNG runs tests randomly
• Believing TestNG skips tests automatically
• Assuming TestNG runs tests only once without control

2. Which of the following is the correct way to set test priority in TestNG?

easy

A. @Test(priority = 1)

B. @Test(order = 1)

C. @Test(sequence = 1)

D. @Test(rank = 1)

Solution

1. Step 1: Recall TestNG annotation syntax

   TestNG uses @Test(priority = number) to set the execution order of tests.

2. Step 2: Identify the correct attribute name

   The correct attribute is priority, not order, sequence, or rank.

3. Final Answer:

   @Test(priority = 1) -> Option A

4. Quick Check:

   TestNG priority syntax = @Test(priority = x) [OK]

Hint: Use 'priority' attribute inside @Test for order [OK]

Common Mistakes:

• Using wrong attribute names like order or rank
• Missing parentheses after @Test
• Confusing priority with dependsOnMethods

3. Given the following TestNG code, what will be the order of test execution?

@Test(priority = 2)
public void testB() { }

@Test(priority = 1)
public void testA() { }

@Test(priority = 3)
public void testC() { }

medium

A. testA, testC, testB

B. testB, testA, testC

C. testA, testB, testC

D. testC, testB, testA

Solution

1. Step 1: Identify priorities assigned to each test

   testA has priority 1, testB has priority 2, testC has priority 3.

2. Step 2: Understand TestNG runs tests in ascending priority order

   Tests run from lowest priority number to highest: 1, then 2, then 3.

3. Final Answer:

   testA, testB, testC -> Option C

4. Quick Check:

   Priority order = 1, 2, 3 [OK]

Hint: Lower priority number runs first in TestNG [OK]

Common Mistakes:

• Assuming higher priority number runs first
• Ignoring priority and expecting alphabetical order
• Confusing priority with dependsOnMethods

4. What is wrong with this TestNG test method if we want testB to run only after testA completes successfully?

@Test
public void testA() { }

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

@Test(dependsOnMethods = {"testC"})
public void testC() { }

medium

A. testA should have dependsOnMethods attribute

B. testB does not depend on testA correctly

C. No errors, code is correct

D. testC depends on itself, causing a circular dependency error

Solution

1. Step 1: Analyze dependencies declared

   testB depends on testA, which is correct. testC depends on "testC" itself, which is a circular dependency.

2. Step 2: Understand circular dependency impact

   A test depending on itself causes TestNG to throw an error and stop execution.

3. Final Answer:

   testC depends on itself, causing a circular dependency error -> Option D

4. Quick Check:

   Self-dependency causes error [OK]

Hint: Avoid tests depending on themselves [OK]

Common Mistakes:

• Thinking testB dependency is wrong
• Adding dependsOnMethods to testA unnecessarily
• Ignoring circular dependency errors

5. You want to run three tests: loginTest, searchTest, and logoutTest. searchTest should run only after loginTest passes, and logoutTest should run last. Which TestNG setup correctly structures this execution?

hard

A. @Test(priority = 1)
public void loginTest() {}

@Test(priority = 2, dependsOnMethods = {"loginTest"})
public void searchTest() {}

@Test(priority = 3)
public void logoutTest() {}

B. @Test(priority = 2)
public void loginTest() {}

@Test(priority = 4, dependsOnMethods = {"loginTest"})
public void searchTest() {}

@Test(priority = 3)
public void logoutTest() {}

C. @Test(priority = 3)
public void loginTest() {}

@Test(priority = 2, dependsOnMethods = {"logoutTest"})
public void searchTest() {}

@Test(priority = 1)
public void logoutTest() {}

D. @Test(priority = 1)
public void loginTest() {}

@Test(priority = 3, dependsOnMethods = {"logoutTest"})
public void searchTest() {}

@Test(priority = 2)
public void logoutTest() {}

Solution

1. Step 1: Check loginTest priority and dependencies

   loginTest has priority 1 and no dependencies, so it runs first.

2. Step 2: Verify searchTest depends on loginTest and runs second

   searchTest has priority 2 and depends on loginTest, so it runs after loginTest passes.

3. Step 3: Confirm logoutTest runs last with priority 3

   logoutTest has priority 3 and no dependencies, so it runs last.

4. Final Answer:

   loginTest (priority=1), searchTest (priority=2, dependsOnMethods={"loginTest"}), logoutTest (priority=3) -> Option A

5. Quick Check:

   loginTest -> searchTest -> logoutTest with correct priority and dependsOnMethods [OK]

Hint: Use priority ascending and dependsOnMethods for order [OK]

Common Mistakes:

• Setting wrong priority numbers
• Wrong dependsOnMethods causing wrong order
• Making logoutTest depend on searchTest incorrectly