Explore topic-wise InterviewSolutions in .

@FACTORY: A factory will execute all the TEST methods present inside a test class using a separate instance of the respective class with different set of data.

@DataProvider: A test method that uses DataProvider will be executed the specific methods multiple number of times based on the data PROVIDED by the DataProvider. The test method will be executed using the same instance of the test class to which the test method belongs.

@Factory: A factory will execute all the test methods present inside a test class using a separate instance of the respective class with different set of data.

@DataProvider: A test method that uses DataProvider will be executed the specific methods multiple number of times based on the data provided by the DataProvider. The test method will be executed using the same instance of the test class to which the test method belongs.

The maximum number of milliseconds a test case should take.

1. @Test(threadPoolSize = 3, invocationCount = 10, timeOut = 10000)
2. public void testCase1(){

In this example, the function testCase1 will be INVOKED ten times from three DIFFERENT threads. ADDITIONALLY, a time-out of ten SECONDS guarantees that none of the threads will block on this THREAD forever.

The maximum number of milliseconds a test case should take.

In this example, the function testCase1 will be invoked ten times from three different threads. Additionally, a time-out of ten seconds guarantees that none of the threads will block on this thread forever.

The threadPoolSize attribute TELLS to form a thread pool to run the test method through multiple threads.

Note: This attribute is IGNORED if invocationCount is not specified

1. @Test(threadPoolSize = 3, &LT;code CLASS="plain">invocationCount = </code><code class="value">10</code>)
2. public void testCase1(){

In this example, the method testCase1 will be invoked from three different threads.

The threadPoolSize attribute tells to form a thread pool to run the test method through multiple threads.

Note: This attribute is ignored if invocationCount is not specified

In this example, the method testCase1 will be invoked from three different threads.

The invocationcount attribute tells how many TIMES TESTNG should run a test method

1. @Test(invocationCount = 10)
2. public void testCase1(){

In this EXAMPLE, the method testCase1 will be INVOKED ten times.

The invocationcount attribute tells how many times TestNG should run a test method

In this example, the method testCase1 will be invoked ten times.

RUN the TestNG USING command prompt

Open command prompt and USE the below code

1. C:UsersAdminDesktopSTMSeleniumTutorialworkspaceSoftwareTestingMaterial
2. SET classpath=C:UsersAdminDesktopSTMSeleniumTutorialworkspaceSoftwareTestingMaterialbin;C:UsersAdminDesktopSTMSeleniumTutorialworkspaceSoftwareTestingMateriallib*
3. java org.testng.TestNG C:UsersAdminDesktopSTMSeleniumTutorialworkspaceSoftwareTestingMaterialtestng.xml

Run the TestNG using command prompt

Open command prompt and use the below code

TestNG can be invoked in the FOLLOWING ways:

• Using Eclipse IDE
• Using ant BUILD tool
• From the COMMAND LINE
• Using IntelliJ’s IDEA

TestNG can be invoked in the following ways:

We specify the time unit in TEST suites and test CASES is in MILLISECONDS.

We specify the time unit in test suites and test cases is in milliseconds.

Regular EXPRESSION to find @TEST methods CONTAINING keyword “smoke” is as mentioned below.

1. &LT;methods&GT;
2. <include name=".*smoke.*"/>
3. </methods>

Regular expression to find @Test methods containing keyword “smoke” is as mentioned below.

TestNG LISTENERS are USED to configure reports and logging. One of the most widely used listeners in testNG is ITestListener interface. It has methods like onTestStart, onTestSuccess, onTestFailure, onTestSkipped etc. We should implement this interface creating a listener class of our own. NEXT we should add the listeners annotation (@Listeners) in the Class which was created.

TestNG listeners are used to configure reports and logging. One of the most widely used listeners in testNG is ITestListener interface. It has methods like onTestStart, onTestSuccess, onTestFailure, onTestSkipped etc. We should implement this interface creating a listener class of our own. Next we should add the listeners annotation (@Listeners) in the Class which was created.

TestNG offers two ways to produce a report:

Listeners implement the INTERFACE org.testng.ITestListener and are NOTIFIED in real time of when a test starts, PASSES, fails, etc…

Reporters implement the interface org.testng.IReporter and are notified when all the suites have been run by TestNG. The IReporter instance receives a list of OBJECTS that describe the ENTIRE test run.

TestNG offers two ways to produce a report:

Listeners implement the interface org.testng.ITestListener and are notified in real time of when a test starts, passes, fails, etc…

Reporters implement the interface org.testng.IReporter and are notified when all the suites have been run by TestNG. The IReporter instance receives a list of objects that describe the entire test run.

• TESTNG allows TWO WAYS to declare the dependencies.
• Using attributes dependsOnMethods in @TEST ANNOTATIONS 
• Using attributes dependsOnGroups in @Test annotations 

To IGNORE the test CASE we USE the parameter ENABLED = false to the @Test annotation.

1. @Test(enabled = false)

To ignore the test case we use the parameter enabled = false to the @Test annotation.

By using throw new SkipException()

Once SkipException() THROWN, remaining part of that test METHOD will not be executed and CONTROL will goes directly to NEXT test method execution.

1. throw new SkipException("SKIPPING - This is not ready for testing ");

By using throw new SkipException()

Once SkipException() thrown, remaining part of that test method will not be executed and control will goes directly to next test method execution.

To disable the test case we USE the PARAMETER ENABLED = FALSE to the @Test annotation.

@Test(enabled = false)

To disable the test case we use the parameter enabled = false to the @Test annotation.

@Test(enabled = false)

By ADDING the exclude tag in the testng.xml

1. <GROUPS&GT;
2. <run>
3.  <exclude NAME="TestGroupNameToExclude"/>
4. </run>
5. </groups>

By adding the exclude tag in the testng.xml

By adding the EXCLUDE TAG in the testng.xml

1. <classes&GT;
2. <class name="TestCaseName">
3. <METHODS>
4. <exclude name="TestMethodNameToExclude"/>
5. </methods>
6. </class>
7. </classes>

By adding the exclude tag in the testng.xml

we can use “parallel” attribute in testng.xml to accomplish parallel test execution in TestNG

The parallel attribute of suite tag can accept four values:

tests: All the test CASES inside <test> tag of testng.xml file will run parallel

classes: All the test cases inside a java class will run parallel

METHODS: All the methods with @Test annotation will EXECUTE parallel

instances: Test cases in same instance will execute parallel but two methods of two DIFFERENT instances will run in different thread.

<suite name="softwaretestingmaterial" parallel="methods">

we can use “parallel” attribute in testng.xml to accomplish parallel test execution in TestNG

The parallel attribute of suite tag can accept four values:

tests: All the test cases inside <test> tag of testng.xml file will run parallel

classes: All the test cases inside a java class will run parallel

methods: All the methods with @Test annotation will execute parallel

instances: Test cases in same instance will execute parallel but two methods of two different instances will run in different thread.

<suite name="softwaretestingmaterial" parallel="methods">

Groups can also INCLUDE other groups. These groups are called MetaGroups. For example, you might want to define a GROUP all that includes smokeTest and functionalTest.

LET’s modify our testng.xml FILE as FOLLOWS:

1. <groups>
2. <define name="all">
3.  <include name="smokeTest"/>
4.  <include name="functionalTest"/>
5. </define>
6. <run>
7. <include name="all" />
8. </run>
9. </groups>

Groups can also include other groups. These groups are called MetaGroups. For example, you might want to define a group all that includes smokeTest and functionalTest.

Let’s modify our testng.xml file as follows:

TESTNG allows you to perform sophisticated groupings of test methods. Not only can you DECLARE that methods belong to GROUPS, but you can also specify groups that contain other groups. Then TestNG can be invoked and asked to INCLUDE a certain set of groups (or regular expressions) while excluding another set. This gives you maximum flexibility in how you partition your tests and doesn’t require you to recompile anything if you want to run two different sets of tests back to back.

Groups are specified in your testng.xml file and can be found either under the <test> or <suite> tag. Groups specified in the <suite> tag APPLY to all the <test> tags underneath.

1. @Test (groups = { "smokeTest", "functionalTest" })
2. public void loginTest(){
3. System.out.println("Logged in successfully");
4. }

TestNG allows you to perform sophisticated groupings of test methods. Not only can you declare that methods belong to groups, but you can also specify groups that contain other groups. Then TestNG can be invoked and asked to include a certain set of groups (or regular expressions) while excluding another set. This gives you maximum flexibility in how you partition your tests and doesn’t require you to recompile anything if you want to run two different sets of tests back to back.

Groups are specified in your testng.xml file and can be found either under the <test> or <suite> tag. Groups specified in the <suite> tag apply to all the <test> tags underneath.

By using @DataProvider annotation, we can CREATE a Data Driven Framework.

1. @DataProvider(name="getData")
2. public OBJECT[][] getData(){
3. //Object [][] data = NEW Object [rowCount][colCount];
4. Object [][] data = new Object [2][2];
6. data [0][0] = "FirstUid";
7. data [0][1] = "FirstPWD";
9. data[1][0] = "SecondUid";
10. data[1][1] = "SecondPWD";
12. RETURN data;
14. }

By using @DataProvider annotation, we can create a Data Driven Framework.

Parameterized tests ALLOW developers to run the same test over and over again using DIFFERENT VALUES.

There are two WAYS to set these parameters:

• using testng.xml 
• using DATA Providers

Parameterized tests allow developers to run the same test over and over again using different values.

There are two ways to set these parameters:

We use priority attribute to the @Test ANNOTATIONS. In case priority is not set then the test SCRIPTS execute in alphabetical order.

1. // TESTNG INTERVIEW Questions
2. package TestNG;
3. import org.testng.annotations.*;
4. public class PriorityTestCase{
5. @Test(priority=0)
6. public void testCase1() {
7. system.out.println("Test Case 1");
8. }
9. @Test(priority=1)
10. public void testCase2() {
11. system.out.println("Test Case 2");
12. }
13. }

Output:

1. Test Case 1
2. Test Case 2

We use priority attribute to the @Test annotations. In case priority is not set then the test scripts execute in alphabetical order.

Output:

TestNG gives an option for tracing the Exception handling of CODE. You can VERIFY whether a code throws the expected exception or not. The expected exception to VALIDATE while running the test case is MENTIONED using the expectedExceptions attribute value along with @Test annotation.

TestNG gives an option for tracing the Exception handling of code. You can verify whether a code throws the expected exception or not. The expected exception to validate while running the test case is mentioned using the expectedExceptions attribute value along with @Test annotation.

Hard ASSERT throws an AssertException IMMEDIATELY when an assert statement FAILS and test suite CONTINUES with NEXT @Test.

Hard Assert throws an AssertException immediately when an assert statement fails and test suite continues with next @Test.

Soft Assert COLLECTS ERRORS during @Test. Soft Assert does not throw an exception when an assert fails and would continue with the next STEP after the assert statement.

If there is any exception and you WANT to throw it then you need to use assertAll() method as a last statement in the @Test and test suite again continue with next @Test as it is.

Soft Assert collects errors during @Test. Soft Assert does not throw an exception when an assert fails and would continue with the next step after the assert statement.

If there is any exception and you want to throw it then you need to use assertAll() method as a last statement in the @Test and test suite again continue with next @Test as it is.

TestNG Asserts HELP us to verify the condition of the test in the middle of the test run. BASED on the TestNG ASSERTIONS, we will consider a successful test only if it is completed the test run without throwing any exception.

Some of the common assertions supported by TestNG are:

• assertEqual(String ACTUAL,String expected)
• assertEqual(String actual,String expected, String MESSAGE)
• assertEquals(boolean actual,boolean expected)
• assertTrue(condition)
• assertTrue(condition, message)
• assertFalse(condition)
• assertFalse(condition, message)

TestNG Asserts help us to verify the condition of the test in the middle of the test run. Based on the TestNG Assertions, we will consider a successful test only if it is completed the test run without throwing any exception.

Some of the common assertions supported by TestNG are:

We COULD define the parameters in the testng.xml file and then reference those parameters in the source files.

Create a JAVA test class, say, ParameterizedTest.java and add a test method say parameterizedTest() to the test class. This method takes a STRING as input parameter. Add the annotation @Parameters(“browser”) to this method.

1. // TestNG Interview Questions
2. public class ParameterizedTest {
3. @Test
4. @Parameters("browser")
5. public VOID parameterizedTest(String browser){
6. if(browser.equals("firefox")){
7. System.out.println("Open Firefox Driver");
8. }else if(browser.equals("CHROME")){
9. System.out.println("Open Chrome Driver");
10. }
11. }
12. }

The parameter would be passed a value from testng.xml, which we will see in the next step.

We could set the parameter using the below syntax in the testng.xml file. 

<parameter name="browser" value="firefox"/>

Here, name attribute represents the parameter name and value represents the value of that parameter.

We could define the parameters in the testng.xml file and then reference those parameters in the source files.

Create a java test class, say, ParameterizedTest.java and add a test method say parameterizedTest() to the test class. This method takes a string as input parameter. Add the annotation @Parameters(“browser”) to this method.

The parameter would be passed a value from testng.xml, which we will see in the next step.

We could set the parameter using the below syntax in the testng.xml file. 

<parameter name="browser" value="firefox"/>

Here, name attribute represents the parameter name and value represents the value of that parameter.

In a Selenium TestNG PROJECT, we USE testng.xml FILE to configure the complete test suite in a SINGLE file.

Some of the features are as follows:

• testng.xml file allows to include or EXCLUDE the execution of test methods and test groups
• It allows to pass parameters to the test cases
• Allows to add group dependencies
• Allows to add priorities to the test cases
• Allows to configure parallel execution of test cases
• Allows to parameterize the test cases

In a Selenium TestNG project, we use testng.xml file to configure the complete test suite in a single file.

Some of the features are as follows:

In TestNG framework, we NEED to create testng.xml file to create and handle multiple TEST classes. We do configure our test RUN, set test dependency, include or exclude any test, method, CLASS or PACKAGE and set priority etc in the xml file.

In TestNG framework, we need to create testng.xml file to create and handle multiple test classes. We do configure our test run, set test dependency, include or exclude any test, method, class or package and set priority etc in the xml file.

• @BeforeTest
• @AfterTest
• @BeforeClass
• @AfterClass
• @BeforeMethod
• @AfterMethod
• @BeforeSuite
• @AfterSuite
• @BeforeGroups
• @AfterGroups
• @TEST

1. TestNG provides parallel execution of test methods
2. It allows to DEFINE dependency of one test method over other method
3. It allows to assign priority to test methods
4. It allows GROUPING of test methods into test groups
5. It has support for parameterizing test cases using @Parameters annotation
6. It allows data driven testing using @DataProvider annotation
7. It has DIFFERENT assertions that helps in checking the expected and actual results
8. Detailed (HTML) reports

TestNG is a testing framework designed to SIMPLIFY a broad range of testing needs, from UNIT testing to INTEGRATION testing.

TestNG is a testing framework designed to simplify a broad range of testing needs, from unit testing to integration testing.