TestNG annotations (@Test, @BeforeMethod, @AfterMethod) in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of TestNG method execution order

Consider the following TestNG test class. What will be the order of printed output when the tests run?

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 teardown() {
    System.out.println("Teardown");
  }
}

A 2,1,3,5,4,6

B 1,3,2,4,6,5

C 1,2,3,4,5,6

D 2,3,1,5,6,4

💡 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, the sequence is: Setup, Test A, Teardown, Setup, Test B, Teardown.

❓ assertion

intermediate

Correct assertion to verify setup execution

You want to verify that the setup method annotated with @BeforeMethod runs before each test. Which assertion correctly checks that the setup flag is set before the test runs?

Selenium Java

import org.testng.Assert;
import org.testng.annotations.*;

public class SetupTest {
  private boolean setupDone = false;

  @BeforeMethod
  public void setup() {
    setupDone = true;
  }

  @Test
  public void testCheckSetup() {
    // Which assertion below is correct here?
  }
}

A Assert.assertEquals(setupDone, false);

B Assert.assertFalse(setupDone);

C Assert.assertNull(setupDone);

D Assert.assertTrue(setupDone);

💡 Hint

The setupDone flag is set to true in @BeforeMethod before the test runs.

The setup method sets setupDone to true before the test method runs. So inside the test, setupDone should be true. Assert.assertTrue(setupDone) verifies this.

🔧 Debug

advanced

Identify why @AfterMethod is not running

Given the following TestNG test class, why is the teardown method annotated with @AfterMethod never executed?

Selenium Java

import org.testng.annotations.*;

public class DebugTest {

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

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

  @AfterMethod
  public void teardown() {
    System.out.println("Teardown");
  }
}

A The @AfterMethod method always runs even if the test fails, so the problem is elsewhere.

B The @AfterMethod method must be static to run after tests.

C The @AfterMethod method is not running because the test method is failing.

D Because the test throws an exception, @AfterMethod is skipped.

💡 Hint

Check TestNG behavior when tests throw exceptions.

In TestNG, @AfterMethod runs regardless of whether the test passes or fails. So even if the test throws an exception, teardown should run. The problem is not due to the exception.

🧠 Conceptual

advanced

Purpose of @BeforeMethod and @AfterMethod in TestNG

Which statement best describes the purpose of @BeforeMethod and @AfterMethod annotations in TestNG?

A @BeforeMethod runs before each test method; @AfterMethod runs after each test method.

B @BeforeMethod runs once before all tests; @AfterMethod runs once after all tests.

C @BeforeMethod and @AfterMethod run only if the test passes.

D @BeforeMethod and @AfterMethod are used to group tests into suites.

💡 Hint

Think about setup and cleanup for each test method.

@BeforeMethod runs before each test method to prepare the test environment. @AfterMethod runs after each test method to clean up. They do not run once for all tests or depend on test success.

❓ framework

expert

TestNG behavior with multiple @BeforeMethod methods

If a TestNG test class has two methods annotated with @BeforeMethod, how does TestNG execute them before each test method?

A TestNG runs both @BeforeMethod methods in the order they appear in the class before each test.

B TestNG runs both @BeforeMethod methods but the order is not guaranteed before each test.

C TestNG throws a runtime error if multiple @BeforeMethod methods exist.

D TestNG runs only one @BeforeMethod method chosen at random before each test.

💡 Hint

Consider TestNG's handling of multiple configuration methods of the same type.

TestNG allows multiple @BeforeMethod methods. It runs all of them before each test method, but the order is not guaranteed unless specified by @Test(priority) or @BeforeMethod(alwaysRun) with dependencies.