TestNG annotations (@Test, @BeforeMethod, @AfterMethod) in Selenium Java - Build an Automation Script

Verify Google Search page title

Preconditions (3)

Step 1: Open Chrome browser

Step 2: Navigate to https://www.google.com

Step 3: Verify the page title is 'Google'

Step 4: Close the browser

✅ Expected Result: The browser opens Google homepage, the title is exactly 'Google', and browser closes after verification

Automation Requirements - TestNG with Selenium WebDriver

Assertions Needed:

Assert that the page title equals 'Google'

Best Practices:

Use @BeforeMethod to set up WebDriver and open browser

Use @Test to perform the title verification

Use @AfterMethod to close the browser

Use explicit waits if needed (not required here)

Use meaningful method names

Automated Solution

Selenium Java

import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
import org.testng.Assert;
import org.testng.annotations.AfterMethod;
import org.testng.annotations.BeforeMethod;
import org.testng.annotations.Test;

public class GoogleTitleTest {
    private WebDriver driver;

    @BeforeMethod
    public void setUp() {
        // Initialize ChromeDriver
        driver = new ChromeDriver();
        // Open Google homepage
        driver.get("https://www.google.com");
    }

    @Test
    public void verifyGoogleTitle() {
        // Get the page title
        String title = driver.getTitle();
        // Assert title is exactly 'Google'
        Assert.assertEquals(title, "Google", "Page title should be 'Google'");
    }

    @AfterMethod
    public void tearDown() {
        // Close the browser
        if (driver != null) {
            driver.quit();
        }
    }
}

The @BeforeMethod annotation marks the setUp() method to run before each test. It initializes the ChromeDriver and opens the Google homepage.

The @Test annotation marks verifyGoogleTitle() as the test method. It fetches the page title and asserts it equals 'Google'.

The @AfterMethod annotation marks tearDown() to run after each test. It closes the browser to clean up.

This structure ensures the browser opens fresh for each test and closes afterward, keeping tests independent and clean.

Common Mistakes - 4 Pitfalls

Not closing the browser in @AfterMethod

Initializing WebDriver inside the @Test method

Using Thread.sleep instead of proper waits

Not using assertions to verify the title

Bonus Challenge

Now add data-driven testing with 3 different URLs and verify their titles

Show Hint

Practice

1. What is the main purpose of the @BeforeMethod annotation in TestNG?

easy

A. To run a method before each test method to set up the test environment

B. To mark a method as a test case

C. To run a method after all test methods have finished

D. To skip a test method during execution

Solution

1. Step 1: Understand the role of @BeforeMethod

   This annotation is used to run a method before each test method to prepare or set up the environment.

2. Step 2: Differentiate from other annotations

   @Test marks test methods, @AfterMethod runs after each test, and skipping tests uses other annotations.

3. Final Answer:

   To run a method before each test method to set up the test environment -> Option A

4. Quick Check:

   @BeforeMethod = setup before each test [OK]

Hint: BeforeMethod always runs before each test method [OK]

Common Mistakes:

• Confusing @BeforeMethod with @BeforeClass
• Thinking @BeforeMethod runs only once
• Mixing @BeforeMethod with @AfterMethod

2. Which of the following is the correct syntax to mark a method as a test case in TestNG?

easy

A. @BeforeMethod void testMethod() {}

B. @Test void testMethod() {}

C. @AfterMethod void testMethod() {}

D. test void testMethod() {}

Solution

1. Step 1: Identify the annotation for test methods

   @Test is the correct annotation to mark a method as a test case in TestNG.

2. Step 2: Check syntax correctness

   The method signature with @Test void testMethod() {} is valid Java and TestNG syntax.

3. Final Answer:

   @Test void testMethod() {} -> Option B

4. Quick Check:

   @Test marks test methods [OK]

Hint: Use @Test to mark test methods in TestNG [OK]

Common Mistakes:

• Using @BeforeMethod or @AfterMethod instead of @Test
• Missing parentheses in method declaration
• Writing 'test' instead of '@Test'

3. Consider the following TestNG class:

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

  @Test
  public void test1() {
    System.out.println("Test1");
  }

  @Test
  public void test2() {
    System.out.println("Test2");
  }

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

What will be the order of printed lines when this test class runs?

medium

A. Test1
Test2
Setup
Cleanup

B. Setup
Cleanup
Test1
Setup
Cleanup
Test2

C. Setup
Test1
Test2
Cleanup

D. Setup
Test1
Cleanup
Setup
Test2
Cleanup

Solution

1. Step 1: Understand TestNG execution flow

   For each @Test method, @BeforeMethod runs before it and @AfterMethod runs after it.

2. Step 2: Trace the print statements

   First test: Setup -> Test1 -> Cleanup. Second test: Setup -> Test2 -> Cleanup.

3. Final Answer:

   Setup Test1 Cleanup Setup Test2 Cleanup -> Option D

4. Quick Check:

   BeforeMethod and AfterMethod wrap each test [OK]

Hint: BeforeMethod and AfterMethod run around each test [OK]

Common Mistakes:

• Assuming BeforeMethod runs once before all tests
• Assuming AfterMethod runs once after all tests
• Mixing order of print statements

4. Identify the error in the following TestNG code snippet:

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

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

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

medium

A. Missing semicolon after System.out.println("Cleanup")

B. Incorrect annotation @AfterMethod should be @AfterTest

C. setup() method should be static

D. testMethod() must return boolean

Solution

1. Step 1: Check syntax in cleanup() method

   The line System.out.println("Cleanup") is missing a semicolon at the end.

2. Step 2: Verify other parts

   Annotations are correct, methods do not need to be static, and test methods can be void.

3. Final Answer:

   Missing semicolon after System.out.println("Cleanup") -> Option A

4. Quick Check:

   Java statements must end with semicolon [OK]

Hint: Check for missing semicolons in Java code [OK]

Common Mistakes:

• Confusing @AfterMethod with @AfterTest
• Thinking test methods must return boolean
• Assuming setup() must be static

5. You want to run a setup method once before all tests in a TestNG class and a cleanup method after each test method. Which annotations should you use for these methods?

hard

A. @BeforeMethod for setup, @AfterMethod for cleanup

B. @BeforeMethod for setup, @AfterClass for cleanup

C. @BeforeClass for setup, @AfterMethod for cleanup

D. @BeforeTest for setup, @AfterTest for cleanup

Solution

1. Step 1: Identify annotation to run once before all tests

   @BeforeClass runs once before any test methods in the class.

2. Step 2: Identify annotation to run after each test method

   @AfterMethod runs after each test method to clean up.

3. Final Answer:

   @BeforeClass for setup, @AfterMethod for cleanup -> Option C

4. Quick Check:

   BeforeClass = once before all, AfterMethod = after each test [OK]

Hint: Use BeforeClass once, AfterMethod after each test [OK]

Common Mistakes:

• Using BeforeMethod for setup once only
• Using AfterClass for cleanup after each test
• Confusing BeforeTest with BeforeClass