Selenium TestNG Interview Questions & Answers Best New 2025

What We Are Learn:

TestNG Interview Questions: TestNG is a widely used testing framework for Java applications that allows developers to write and run automated tests. It provides features like parallel testing, flexible test configuration, and better reporting capabilities than JUnit. If you’re a Java developer or a software tester, you might have encountered TestNG at some point in your career.

To help you prepare for a TestNG interview, we’ve compiled a list of some of the most commonly asked TestNG interview questions. These questions will cover the basics of TestNG, such as its features, annotations, and configurations, as well as more advanced topics like data-driven testing and parallel execution. By preparing for these questions, you can increase your chances of landing your dream job and showcase your knowledge of TestNG.

To improve your knowledge of TestNG, we also wrote a dedicated TestNG Tutorial, in which we share all possible TestNG Concepts and how to implement those various testing scenarios in your automation test script.

Testers who have already used TestNG in their projects can directly jump to the TestNG interview questions. But for those who have just started learning TestNG, we highly recommend going through the TestNG tutorial first.

Interview Questions On TestNG

What is the importance of the TestNG framework?
Why do we use TestNG in your framework?
Explain the purpose of listeners. Is it the selenium concept of TestNG?
What is the purpose of testing XML
Case Scenario: How to run the same method 100 times in TestNG with the same data?
What is the reporting tool in your framework? and why?
Some questions in TestNG XML?
What are different TestNG annotations?
How can you configure tests in TestNG?
What is @dataprovider?
What is the difference between @Factory and @DataProvider?
@Factory explain with real-time example?
Test Order in TestNG?
How to add/remove test cases in Testng.xml?
Explain the difference between beforemethod, beforetest, and beforeclass
List out the TestNG annotation hierarchy order.
How do you achieve parallel execution using TestNG?
Out of 50 test cases, how will you run only the failed test cases?
How can you take screenshots of the failed test cases?
How can you run the same tests ten times?
Types of Listeners?
TestNG: Parallel executions, Grouping?
What is the difference between @aftersuite and @beforesuite?
What is the use of testng.xml?
How many suits can be in TestNG? What if I run all the suits?
Syntax to perform parallel testing in TestNG and what do you write in also, what do you mention in double-quotes like parallel = “ ”
In TestNG, do we have multiple suites in one XML file, and what If I want to run all suits?
What is the invocation count in TestNG?
Cucumber tags and annotations?
What is your background in Cucumber?
What is the difference between a Scenario and a Scenario Outline?
Write the skeleton of the test runner.
Explain the retry analyzer.
Cucumber tags? And how to run different combinations of tags when multiple tags are present
What is the difference between hooks and tags?
One @test is there; would you like to give it a chance three times whenever it fails?
What is TestNG?
What TestNG Annotations do you use in the project?
How to run multiple test cases
Difference between BeforeSuite and BeforeMethod
Hierarchy of TestNg Annotations
How to run a group of test cases in TestNg
How to include or exclude test cases in TestNg
How to run the parallel test case in TestNg
What different test annotations have you used in TestNg?
How to run failed test cases in TestNg
What is a Listener?
What is DataProvider?
What is parameterization?
What is PageFactory?
Should know all TestNG annotations.
How do you group the test cases? And why?
How to rerun failed TC 3 times.
How to take ss of failed TC.
Assert and Verify
How will you generate Reports?
What is dependency injection in cucumber and TestNG, and how can we achieve it?
TestNg sequence.
Why is no main method required in TestNG execution?

TestNG Interview Questions

Why should we prefer using WebDriver instead of Selenium IDE?
What is the easiest way to get the value from a text field in Selenium?
What is the best approach to reading a JavaScript variable from Selenium WebDriver?
How will you get the HTML source of an <WebElement> in Selenium WebDriver using Python/Java/C#?
How to initialize a list of web elements in Selenium Webdriver?
What is the best way to click screenshots when a test fails in Selenium 2.0?
How do I fix the Chrome driver error below in Selenium?
What is the right way to run Selenium WebDriver test cases in Chrome?
What to do for setting up the <InternetExplorerDriver> for Selenium 2.0?
What would you do to make the <WebDriver> wait for a page to refresh before executing the test?
How do I get the Selenium to wait until the document is ready?
How to get Selenium to wait until the element is present?
What is the fundamental difference between wait () and sleep()?
How can we run a particular TestNG test group using a maven command?
Which command will you use to run a single test method in Maven?
How can we run all the tests of a TestNG class?
How will you run the Selenium tests without using the <testng.xml>?
How to disable an entire Selenium test in TestNG?
How can we attach a failure screenshot to the testNG report?
What would you do to configure the parallel execution of tests and classes in <testng.xml>?

Test NG Interview Questions

Annotations in TestNG
Difference between @BeforeTest and @BeforeMethod
Soft assert vs Hard Assert
How to pass parameters to test methods
Use of data provider
Use of invocationCount, enabled, priority, dependsOnMethod, dependsOnGroups, alwaysRun, dataProvider, groups, timeout, expectedExceptions, singleThreaded, etc
TestNg XML structure
How to group test cases
Use of IRetryAnalyzer class
How to run failed test cases
How to perform parallel testing.
What level of user can perform parallel testing
Use of ISuiteListener Methods
Use of TestListenerAdaptor methods
How to ignore packages and classes.
Can the user provide a negative value for setting priority?

Interview Questions On TestNG For Experienced

All Documents on the official testNG website- annotations
Soft assertions using TestNG and Custom soft assertions.
TestNG, TestNG XML, TestNG API
Customized TestNG Report
Parallel testing and Threading usage
What are groups in TestNG, and how can we execute particular group test cases?
Different annotation sequence
What is Parameterized testing in TestNG
Data Providers
What is the use of @Listener annotation in TestNG

TestNG Annotation Execution Flow Selenium Example Program?

package com.selenium.TestNG;
import org.testng.annotations.AfterClass;
import org.testng.annotations.BeforeClass;
import org.testng.annotations.BeforeMethod;
import org.testng.annotations.BeforeTest;
import org.testng.annotations.Test;
public class FlowTestClass1 
{
   @BeforeTest
   public void beforetest2()
   {
      System.out.println("Class 1 Before Test");
   }
   @BeforeClass
   public void beforeclass1()
   {
      System.out.println("Class 1 Before Class");
   }
   @BeforeMethod
   public void beforemethod1()
   {
      System.out.println("Class 1 Before Method");
   }
   @Test
   public void class1test1()
   {
      System.out.println("Inside Class 1 Test1");
   }
   @Test
   public void class1test2()
   {
      System.out.println("Inside Class 1 Test2");
   }@AfterClass
   public void Afterclass1()
   {
      System.out.println("Class 1 After Class");
   }
}

package com.selenium.TestNG;
import org.testng.annotations.AfterClass;
import org.testng.annotations.AfterTest;
import org.testng.annotations.BeforeClass;
import org.testng.annotations.BeforeTest;
import org.testng.annotations.Test;
@Test
public class FlowTestClass2 
{
   @BeforeTest
   public void beforeTest0()
   {
      System.out.println("Class 2 Before Test");
   }
   @BeforeClass
   public void beforeClass2()
   {
      System.out.println("Class 2 Before Class");
   }
   @Test
   public void class2test1()
   {
      System.out.println("Class 2 Test1");
   }
   @AfterClass
   public void AfterClass()
   {
      System.out.println("Class 2 After Class");
   }
   @AfterTest
   public void aftertest()
   {
      System.out.println("Inside Class2 After Test");
   }
}

How will you execute methods or test cases in TestNG in a different order/your order?
We can control the order of method execution in TestNG by using various attributes and annotations. Here are some examples of how to execute methods or test cases in a specific order:

Priority attribute usage
Using the dependsOnMethods attribute
Using the dependsOnGroups property
Making use of an XML configuration file

How to pass the parameter in the test case through the testng.xml file?
You can use the parameter tag within the test tag to pass parameters in the test case via the TestNG XML file. First, You need to specify the parameter name and value within the tag. These parameters can be accessed in the test case by using the @Parameters annotation in the method signature, as shown below:

@Test 
@Parameters("username", "password")
public void myTestMethod(String username.String password)
{
   // Test Method Code
}

What is the difference between @Factory and @Dataprovider annotations?
The @Factory annotation is used to create multiple instances of the same test class, each with a different set of input parameters or configurations. This is useful when running the same test with different data sets or configurations or when running tests in parallel to save time during testing.

Meanwhile, the @DataProvider annotation supplies test data to a test method. It allows you to separate the test data from the test logic, making your test code easier to maintain and reuse. @DataProvider can be used to provide test data from various sources, including arrays, Excel sheets, databases, and external files.

What is the use of @Listener annotation in TestNG?
In TestNG, the @Listener annotation defines listeners, which are classes that listen to events that occur during a test’s execution. Listeners can be used to customize or enhance TestNG’s behavior by adding extra functionality such as logging, reporting, or customizing the test execution.

You can specify one or more listener classes to be invoked during test execution by using the @Listener annotation.

What are the attributes supported by @Test annotation in TestNG?
The following is an exhaustive list of the attributes supported by the @Test annotation in
TestNG:

alwaysRun
dataProvider
description
expectedExceptions
groups
invocationCount
invocation Time Out
priority
timeOut
dependsOnGroups
dependsOnMethods
skipFailedinvocations

What is the difference between Suite, Test, and Class?
Suite: The highest level of organization in TestNG is a suite. It is a set of one or more tests that can be run concurrently. A suite may include several tests, configurations, and other elements such as listeners, parameters, and groups.

Test: A test is a collection of related test cases that can be executed concurrently. A test may contain one or more classes and various parameters and configurations.
Class: A class is a Java class that contains one or more test methods. Test methods are marked with @Test and run as part of a test. A class can also contain methods for setting up or tearing down the test environment.

Priority attribute usage
Using the dependsOnMethods attribute
Using the dependsOnGroups property
Making use of an XML configuration file

Why do we create the XML file in TestNG?
The XML file is used in TestNG to configure and customize the test execution process. It contains elements and attributes that define the suite, test cases, test methods, groups, listeners, and other settings that govern how the tests are run.

Here are some reasons why we should create an XML file in TestNG:

The XML file allows you to configure the test suite, set parameters, and tailor the test execution process to your specific needs.
You can specify the priority of test methods, and TestNG will execute them in the order you specify.
You can group the test methods based on their functionalities and execute only the necessary group of methods.
The test parameters can be specified in the XML file, and TestNG will pass those parameters to the test methods at runtime.
it allows you to specify which test methods can be executed concurrently, and TestNG will execute them concurrently, saving you time.

Write the code snipped for passing values 1 and 2 to the parameters val1 and val2 through the XML file.
Here’s an example of code that shows how to use the XML file to pass values 1 and 2 to the parameters “val1” and “val2”:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "https://testng.org/testng-1.0.dtd">
<suite name="Suite">
  <test thread-count="5" name="Test">
    <packages>
      <package name="com.softwaretestingo.testng.attributes"/>
      <package name="com.softwaretestingo.testng"/>
    </packages>
  </test> <!-- Test -->
</suite> <!-- Suite -->

How do we integrate TestNG XML with Maven?
Add the TestNG dependency to your Maven pom.xml file, create a TestNG XML file and add your test classes and configurations, add the maven-surefire-plugin to the build section of your pom.xml file, and run your Maven tests using the test command to integrate TestNG XML with Maven.

You can use the example below as a reference to add the maven-surefire-plugin to the build section of your Maven pom.xml file and specify the TestNG XML file to use.

<build> 
	<plugin>
		<groupid>org.apache.maven.plugins</groupid>
		<artifactld>maven-surefire-plugin</artifactld>
		<version>3.0.0-M5</version>
		<configuration>
			<suiteXmIFiles>
				<suiteXmiFile>src/test/resources/testng.xml</suiteXmiFile>
			</suiteXmIFiles>
		</configuration>
	</plugin>
</plugins>
</build>

What are the types of annotations used in TestNG (In the sequence of execution/hierarchy)?
Before Suite
Before Test
Before Clared
Test 1
After Method
Before Method
Test 2
After Method
After Class
After Test
After Suite

What is @Factory annotation in TestNG?
In TestNG, the @Factory annotation is used to create test instances at runtime. It enables you to generate test classes or instances dynamically based on runtime conditions or parameters. You can use the @Factory annotation to create multiple instances of the same test class with different data sets or parameters and run them in parallel to improve test execution speed. Here is an example of @factory annotations.

@Factory
public static Object[] createinstances()
{
	Object] result = new Object[3):
	for(int i=0; i<result.length; i++)
	{
		result[i]= new MyTest());
	}
	return result:
}

Using the @Listener annotation, you can specify one or more listener classes to be invoked during test execution. This enables you to extend and customize TesiNG’s behavior to meet your specific testing requirements.

What is the sequence of execution of the annotations in TestNG?
The annotations are executed in the following order TestNG

@BeforeSuite
@BeforeTest
@BeforeClass
@BeforeMethod
@TestMethod
@AfterMethod
@AfterClass
@AfterTest
@AfterSuite

What are the attributes supported by @ Test annotation in TestNG?
The following is an exhaustive list of the attributes supported by the @Test annotation in TestNG:

alwaysRun
dataProvider
dataProviderClass
description
enabled
expectedExceptions
expectedExceptionsMessageRegExp
groups
invocationCount
Invocation TimeOut
priority
successPercentage
testName
timeOut
dependsOnGroups
dependsOnMethods
skipFailedinvocations
alwaysResolveDependencies

What is the use of the dependsOnMethods attribute in TestNG?
The dependsOnMethods attribute in TestNG is used to specify a test method’s dependency on one or more other test methods. This property allows us to ensure that certain test methods are run in the correct order.

When one test method is dependent on another, TestNG will not run the dependent method until all of its dependencies have passed successfully. If any of the dependencies fail or are skipped, the dependent method will be skipped.

What is the use of the dependsOnGroups attribute in TestNG?
The dependsOnGroups attribute in TestNG specifies a test method’s dependency on one or more groups of test methods. This property allows us to ensure that certain groups of test methods are executed in the correct order.

When a test method is dependent on a group of test methods, TestNG will not execute the dependent method until all of the test methods in the specified group have successfully passed. If any of the group’s test methods fail or are skipped, the dependent method will also be skipped.

How do you define groups in TestNG?
Groups are collections of multiple test case methods combined into a single unit. We can operate directly on the group by grouping, which will reflect on all of the test case methods under it. Furthermore, in TestNG, we can define a group of groups as a larger unit of test methods.

How do you exclude a group from the test execution cycle?
The exclusion of a group in TestNG indicates that this group will not run throughout the execution and will be ignored by TestNG. Furthermore, the name of the group to be excluded is defined in the XML file using the following syntax:

<groups>
	<run>
		<exclude name="TestNG testing"></exclude>
	</run>
</groups>

How to create a Group of Groups in TestNG?
You can make a group of groups in TestNG by including one or more groups as dependencies
on another group. The following are the steps for creating a group of groups in TestNG:
In your test class, use the @Test annotation with the groups attribute to define groups. As an
example:

@Test(groups = {"group1"})
public void testMethod1()
{
	// Test Code
}
@Test(groups = {"group2"})
public void testMethod2()
{
	// Test Code
}
@Test(groups = {"group3"})
public void testMethod3()
{
	// Test Code
}

How to group multiple test methods with Priority?
The priority attribute of the @Test annotation in TestNG allows you to group multiple test methods with different priorities. The priority attribute specifies the order in which TestNG should execute the test methods.

To divide a test method into numerous groups, use the groups attribute to give a comma-separated list of group names. As an example:

@Test(priority=1, groups = {"Maths"})
public void testMethod1()
{
	// Test Code
}
@Test(priority=2, groups = {"Maths"})
public void testMethod2()
{
	// Test Code
}

Describe any five common TestNG assertions.

assertE quals(expectedValue, actualValue, message): It compares two values and determines if they are equal.
assertTrue(condition, message): This assertion helps determine whether or not the specified condition is true.
assertFalse(condition, message): This assertion defines if the specified condition is true or false.
assertNull(object, message): This assertion determines whether or not the specified object is
assertNotNull(object, message): This assertion specifies if the specified object is null.

Define soft assert in Testing and describe how they are different from hard assert.
Soft assertions in TestNG mean that the tests will continue to run even if the assertion throws an exception in the middle of the execution. Furthermore, TestNG does not include Soft asserts by default, so an additional org.testng.asserts.Softassert package import is required.

Soft assertions differ from hard assertions in that when a hard assertion fails, the test terminates immediately, and the remaining test steps are skipped. When a soft assertion fails, however, the test continues to run, and any subsequent assertions are also run. Only when the test is completed are the test results, including soft assertion failures, reported, but the test is not terminated.

What is meant by dependency in TestNG?
Dependencies are used in TestNG to specify the order in which test methods should be executed. A dependency is a relationship between two or more test methods that specifies that one or more tests must be run before another.

Here is an example of dependency:

@Test(dependsOnMethods = {"testMethod1"})
public void testMethod2()
{
	// Test Methods Code
}
@Test
public void testMethod1()
{
	// Test Methods Code
}

What is the significance of “timeout” in TestNG?
The timeout attribute in TestNG is used to specify the maximum amount of time (in milliseconds) that a test method should be allowed to run before being forcefully terminated. This property is useful when a test method becomes stuck in an infinite loop or takes too long to complete, causing the entire test suite to stall. It can be declared at

Suite level: To impose a time limit on all methods in the suite.
Method level: To impose a time constraint on a specific method.

Syntax:
@Test(timeout = 5000)

What is meant by invocationCount in TestNG?
The invocationCount attribute specifies how many times a test method must be executed in a single execution. Hence, if I set the invocation Count to 5, the test function will be invoked five times each time I run the TestNG test case.

Code for invocationCount: @Test (invocationCount = 10) |

What is meant by parallel test execution in TestNG?
Parallel test execution in TestNG means running multiple test cases or test suites on multiple threads at the same time. TestNG is designed to support the parallel execution of tests, which allows testers to run multiple tests concurrently, reducing overall test execution time.

There are two ways to for parallel testing in TestNG:

Parallel tests at the method level
Parallel tests at the suite level

On what levels can we apply parallel testing in TestNG?
Parallel testing is possible in TestNG at multiple levels:

Methods: This will run all @Test methods in TestNG in parallel.
Tests: This value will be used to run all test cases contained within the ‹test>tag
Classes: All of the test cases contained within the XML classes will run in parallel.
Instances: This value will run all test cases concurrently within the same instance.

How to achieve TestNG itestlistener implementation? (USED for REPORTING in Automation Frameworks)
Sure, here are the step-by-step instructions for implementing TestNG ITestListener:

Make a Java class that conforms to the ITestListener interface.
Override the necessary methods like onStart(), onTestSuccess(), onTestFailure(), onTestSkipped(), and onFinish().
In each of these methods, add the custom actions you want to perform, such as logging, reporting, or modifying test results.
Make a separate Java file for the listener class.
Include the tag and specify the full class name of your listener in your TestNG XML
configuration file to add the listener class.
Alternatively, you can use the @Listeners annotation on your test class and specify the full class name of your listener.
When you run your test suite, the listener methods will be executed in response to the test events, allowing you to take custom actions.

How can we create a data-driven framework using TestNG?
You can use TestNG to build a data-driven framework by following these steps:

Make a TestNG XML file with the test parameters and data provider. A data provider is a method that provides test data to other methods.
Implement the data provider method to get test data from a data source like a CSV file, Excel sheet, or database.
Add the data provider attribute to the @Test annotation of the test method to indicate that the data provided by the data provider method will be used by the test method.
Use the test data to execute the test logic in the test method.

@Test(dataProvider ="testData")
public void testMethod(String firstName, String lastName, int age)
{
	System.out.println("Name:" + firstName + "" + lastName +", Age:" + age);
	// Test Logic Using the Test Data
}

What is the use of@Test(threadPoolSize=x)?
In TestNG, the @Test(threadPoolSize=x) annotation specifies the number of threads to use when running a test method in parallel. The x parameter is an integer value that indicates the thread pool size.

When you use this annotation, TestNG will create a pool of threads and distribute test method instances among them. Each thread will independently and concurrently execute its assigned test method instance with the other threads.

How to implement Data providers in TestNG?
Follow these steps to add data providers to TestNG:

Create a method that returns an array of two-dimensional objects. Each array row represents a set of test data.

@DataProvider(name ="testData")
public Object[][] testData() 
{
	return new Object[][]
	{
		{"Mehul", "password1"},
		{"Gadhiya","password2"},
		{"Devya","password3"}
	}
}

Add the @DataProvider annotation to the method and give the data provides a name.
Add the dataProvider attribute to the @Test annotation in the test method and set it to the data provider’s name.

@Test(dataProvider="testData")
public void tesLogin(String username, String password)
{
	// Test Code Goes Here
}

Add parameters to the test method to receive test data. In the preceding example, we have two parameters, username and password, which will be set to the data provider’s values. Use the test data in the test method to perform the test and assert the results.

Explain how you can achieve parallel test execution in TestNG, and what are the key attributes for parallel configuration?
Answer: Parallel execution in TestNG can be achieved using the parallel attribute at the suite, test, or method level. Key attributes include methods, tests, instances, and classes.

How can you implement data-driven testing in TestNG, and what annotations or attributes are involved?
Answer: Data-driven testing is achieved using the @DataProvider annotation and associating it with the dataProvider attribute in the @Test annotation.

Describe how you handle test dependencies in TestNG and what annotations are used for this purpose.
Answer: TestNG allows dependency management using the dependsOnMethods and dependsOnGroups attributes within the @Test annotation.

How do you group tests in TestNG, and what mechanisms are available to control the execution of specific groups?
Answer: Tests can be grouped using the @Test(groups = “group_name”) annotation. Execution control involves including or excluding specific groups in the XML suite file.

Explain the role of listeners in TestNG and how you can generate detailed test reports using listeners.
Answer: Listeners like IInvokedMethodListener and ITestListener allow you to customize test behavior and generate detailed reports. Utilize tools like Extent Reports for enhanced reporting.

How can you parameterize your tests in TestNG, and what is the significance of the @Parameters annotation?
Answer: Test parameterization is achieved using the @Parameters annotation in conjunction with the parameter attribute in the @Test annotation.

What is a TestNG suite, and how can you configure and run multiple test classes using XML configuration?
Answer: A TestNG suite is a collection of test classes. Configuration is done using the XML suite file, where you define test classes, groups, and parameters.

How can you handle expected exceptions in TestNG, and what annotations are involved?
Answer: Use the @Test(expectedExceptions = Exception.class) annotation to handle expected exceptions during test execution.

Explain the concept of soft assertions in TestNG and how they differ from traditional assertions.
Answer: Soft assertions, provided by the SoftAssert class, allow the execution of subsequent test steps even if an assertion fails, providing a comprehensive test report.

Discuss how you integrate TestNG with Selenium for automated testing, and what are the benefits of this integration.
Answer: TestNG and Selenium integration involves creating test scripts using TestNG annotations, which allows for better test organization, parallel execution, and reporting.

Final Words

The above testNG interview questions can be compiled after interacting with many candidates who have already attended some of the interviews. Many candidates face these questions in different interviews; they have applied for the job position from fresher to an experienced level.

From the list, you can find some of the interview questions I faced when I was interviewed. That’s why these are the best test engineer interview questions, which can help you gain confidence in answering those testNG interview questions.

TestNG Interview Questions

Interview Questions On TestNG

TestNG Interview Questions

Test NG Interview Questions

Interview Questions On TestNG For Experienced

Softwaretestingo Editorial Board

Leave a Comment Cancel reply