Why TestNG structures test execution in Selenium Java - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of TestNG Test Execution Structure

Why does TestNG organize tests using annotations like @BeforeMethod, @Test, and @AfterMethod?

A To make tests run only once without any setup or cleanup

B To force tests to run in alphabetical order by method name

C To control the order of test execution and setup/cleanup steps automatically

D To disable parallel execution of tests by default

💡 Hint

Think about how setup and cleanup code can be reused for each test.

TestNG uses annotations to structure test execution so that setup and cleanup methods run automatically before and after each test. This ensures tests run in a controlled environment and reduces code duplication.

❓ Predict Output

intermediate

TestNG Execution Order Output

What will be the output order when running this TestNG test class?

Selenium Java

import org.testng.annotations.*;

public class SampleTest {

  @BeforeMethod
  public void setup() {
    System.out.println("Setup");
  }

  @Test
  public void testA() {
    System.out.println("Test A");
  }

  @Test
  public void testB() {
    System.out.println("Test B");
  }

  @AfterMethod
  public void cleanup() {
    System.out.println("Cleanup");
  }
}

A

Setup
Cleanup
Setup
Cleanup
Test A
Test B

B

Test A
Test B
Setup
Cleanup
Setup
Cleanup

C

Setup
Test A
Test B
Cleanup
Cleanup

D

Setup
Test A
Cleanup
Setup
Test B
Cleanup

💡 Hint

Remember that @BeforeMethod and @AfterMethod run before and after each @Test method.

TestNG runs @BeforeMethod before each test method and @AfterMethod after each test method. So for two tests, setup and cleanup run twice, surrounding each test.

❓ assertion

advanced

Correct Assertion for TestNG Test Result

Which assertion correctly verifies that a web page title equals "Home Page" in a TestNG Selenium test?

Selenium Java

String actualTitle = driver.getTitle();

A Assert.assertEquals(actualTitle, "Home Page");

B Assert.assertTrue(actualTitle = "Home Page");

C Assert.assertEquals("Home Page", actualTitle, false);

D Assert.assertTrue(actualTitle.equalsIgnoreCase("Home Page"));

💡 Hint

Check the correct method signature for equality assertion in TestNG.

Assert.assertEquals(actual, expected) is the correct way to check equality in TestNG. Option A uses assignment instead of comparison, C has an invalid third argument, and A ignores case which may not be desired.

🔧 Debug

advanced

Identify the TestNG Execution Problem

Given this TestNG test class, why does the @AfterMethod not run after testLogin?

Selenium Java

import org.testng.annotations.*;

public class LoginTest {

  @BeforeMethod
  public void setup() {
    System.out.println("Setup");
  }

  @Test
  public void testLogin() {
    System.out.println("Login Test");
    throw new RuntimeException("Fail");
  }

  @AfterMethod
  public void cleanup() {
    System.out.println("Cleanup");
  }
}

A Because the exception in testLogin stops the @AfterMethod from running

B Because @AfterMethod is missing the alwaysRun=true attribute

C Because @BeforeMethod and @AfterMethod must be static methods

D Because @AfterMethod only runs if @Test passes without exceptions

💡 Hint

Consider how TestNG handles cleanup when tests throw exceptions.

By default, if a test method throws an exception, @AfterMethod may not run unless it has alwaysRun=true. Adding this attribute ensures cleanup runs even if the test fails.

❓ framework

expert

TestNG Parallel Execution Behavior

When TestNG is configured to run tests in parallel by methods, what is the expected behavior regarding @BeforeMethod and @AfterMethod?

A <code>@BeforeMethod</code> and <code>@AfterMethod</code> run in the same thread as their test method, independently for each test

B <code>@BeforeMethod</code> and <code>@AfterMethod</code> run sequentially in the main thread regardless of parallel tests

C <code>@BeforeMethod</code> runs once before all tests, and <code>@AfterMethod</code> runs once after all tests

D <code>@BeforeMethod</code> and <code>@AfterMethod</code> are skipped when tests run in parallel

💡 Hint

Think about thread safety and how setup/cleanup should behave when tests run at the same time.

In parallel execution by methods, TestNG runs each test method in its own thread. The @BeforeMethod and @AfterMethod run in the same thread as their test method, ensuring isolated setup and cleanup.