To simplify this we will use TestNG DataProvider concept. Will read multiple sets of data from excel and will place the same in dataprovider object array and will pass the same to the test method as parameters. Here, we need to remember one thing is; dataprovider array values and test method parameter values must be same.

We will take one sample program to read data from excel to dataprovider. Here to interact with the excel sheet will use Apache POI api.  Will read some sample data from excel to dataprovider and will print the same.

Below is the sample Excel File:

Below is the sample program:

import org.testng.annotations.DataProvider;
import org.testng.annotations.Test;

public class ExcelToDataProvider {
    
    String xlFilePath = "/KRISHNA VOLUME/Jar Files/poi-3.16-beta1/TestData.xlsx";
    String sheetName = "Credentials";
    ExcelApiTest eat = null;
    
    @Test(dataProvider = "userData")
    public void fillUserForm(String userName, String passWord, String dateCreated, String noOfAttempts, String result)
    {
       System.out.println("UserName: "+ userName);
       System.out.println("PassWord: "+ passWord);
       System.out.println("DateCreated: "+ dateCreated);
       System.out.println("NoOfAttempts: "+ noOfAttempts);
       System.out.println("Result: "+ result);
       System.out.println("*********************");
    }
    
    
    @DataProvider(name="userData")
    public Object[][] userFormData() throws Exception
    {
        Object[][] data = testData(xlFilePath, sheetName);
        return data;
    }
    
    public Object[][] testData(String xlFilePath, String sheetName) throws Exception
    {
        Object[][] excelData = null;
        eat = new ExcelApiTest(xlFilePath);
        int rows = eat.getRowCount(sheetName);
        int columns = eat.getColumnCount(sheetName);
                
        excelData = new Object[rows-1][columns];
        
        for(int i=1; i<rows; i++)
        {
            for(int j=0; j<columns; j++)
            {
                excelData[i-1][j] = eat.getCellData(sheetName, j, i);
            }
            
        }
        return excelData;
    }
}

In the above program, fillUserForm() is a test method and will accept 5 parameters. So, we need to read data from excel to dataprovider to pass these 5 parameters multiple times. For this we will use testData() method to read the data from the excel sheet using Apache POI. It takes two parameters called excel file path and sheet name. By using these two parameters it will read the excel data and store in Object array.

userFormData() is actually a dataProvider to pass the data to test method. It will get the data from the testData() method and the return type of this method is Object array. We have separated this testData() method from the dataProvider because there is a chance of using the same logic more than one test method. In this scenario we can use the same testData() method to create a separate dataProvider for each and every test method to get the parameters.

Output of the above program is:

Can get the code for how we can get row count and column count in excel here.

Please watch the youtube video for better understanding and more examples.

The post Read data from Excel to DataProvider in Selenium appeared first on Selenium Webdriver Appium Complete Tutorial.

Running testng tests programmatically will discuss about how to execute testng tests programmatically.  Till now we have executed all the tests using testng.xml file in the previous blogs. In this blog, will see how to avoid xml file (i.e testng.xml) and execute the same functionality using java file(i.e. programmatically).

We have some limitations with the xml file that xml files are static and can not be changed at runtime. As per the requirement sometimes we need to change some of the configurations at runtime, which is depends on an Excel sheet or database data interaction. To achieve these kinds of things TestNG provided a feature to define and execute TestNG tests through program by using some of the APIs provided by the TestNG.

All the things which is possible with the testng.xml file can be achieved by the API provided by TestNG. And after completion of writing the program we can easily execute the code as this is a normal java file.

Below are the two sample programs we can execute these files using testng program.

First Sample java file:

import org.testng.Assert;
import org.testng.annotations.Test;

public class SampleProgramOne {
    @Test
    public void testOne() {
        Assert.assertTrue(true);
        System.out.println("Pass Test case - testOne");
    }

    @Test
    public void testTwo() {
        Assert.assertEquals("AutomationgTesting", "AutomationgTest");
        System.out.println("Pass Test case - testOne");
    }

    @Test
    public void testThree() {
        Assert.assertTrue(true);
        System.out.println("Pass Test case - testThree");
    }
}

Second Sample java file:

import org.testng.annotations.AfterMethod;
import org.testng.annotations.BeforeMethod;
import org.testng.annotations.Test;

public class SampleProgramTwo {

    @BeforeMethod
    public void beforeMethod() {
        System.out.println("I am in beforeMethod");
    }

    @Test
    public void testOne() {
        System.out.println("I am in Simple Test");
    }

    @AfterMethod
    public void afterMethod() {
        System.out.println("I am in afterMethod");
    }
}

Using Listeners is mandatory while executing the suite through code. Otherwise it will not show the errors information in detail. Means, which method got failed and what is exact error message will not be given if you not using the listeners. Below is the sample listener class.

import org.testng.ITestContext;
import org.testng.ITestListener;
import org.testng.ITestResult;

public class ListenerTest implements ITestListener {

    @Override
    public void onTestStart(ITestResult result) {
        // TODO Auto-generated method stub

    }

    @Override
    public void onTestSuccess(ITestResult result) {
        // TODO Auto-generated method stub

    }

    @Override
    public void onTestFailure(ITestResult result) {
        System.out.println(result.getName() + " : " + result.getThrowable());

    }

    @Override
    public void onTestSkipped(ITestResult result) {
        // TODO Auto-generated method stub

    }

    @Override
    public void onTestFailedButWithinSuccessPercentage(ITestResult result) {
        // TODO Auto-generated method stub

    }

    @Override
    public void onStart(ITestContext context) {
        // TODO Auto-generated method stub

    }

    @Override
    public void onFinish(ITestContext context) {
        // TODO Auto-generated method stub

    }
}

In the above program, result.getName() will give the method name which is failed and result.getThrowable() will give the exact error message.
Below is the testng java configuration file which is the replacement for testng.xml file:

import java.util.ArrayList;
import java.util.List;

import org.testng.TestNG;
import org.testng.xml.XmlClass;
import org.testng.xml.XmlSuite;
import org.testng.xml.XmlTest;

public class TestNgXmlUsingCode {
    public void testNgXmlSuite() {

        List<XmlSuite> suites = new ArrayList<XmlSuite>();
        List<XmlClass> classes = new ArrayList<XmlClass>();
        List<Class> listenerClasses = new ArrayList<Class>();

        XmlSuite suite = new XmlSuite();
        suite.setName("ProgramSuite");

        XmlTest test = new XmlTest(suite);
        test.setName("ProgramTest");

        XmlClass clss1 = new XmlClass("SampleProgramOne");
        classes.add(clss1);

        XmlClass clss2 = new XmlClass("SampleProgramTwo");
        classes.add(clss2);

        listenerClasses.add(ListenerTest.class);

        test.setXmlClasses(classes);

        suites.add(suite);

        TestNG tng = new TestNG();

        tng.setXmlSuites(suites);
        tng.setListenerClasses(listenerClasses);
        tng.run();
    }

    public static void main(String[] args) {
        TestNgXmlUsingCode tnxuc = new TestNgXmlUsingCode();
        tnxuc.testNgXmlSuite();
    }
}

The above program is the testng configuration file which is replacement of testng.xml file creating programmatically. By executing the above java program normally we can achieve the same functionality which is available with xml file.

Below is the output of the above program:

This output look is different from the testng,.xml configuration file output.
In the above program, XmlSuite is equal to suite tag in testng.xml file, XmlTest is equal to test tag, XmlClass is equal to class tag.
This way we can create testng.xml file programmatically in TestNG.
Please watch You tube video for better understanding.

The post Running TestNG Tests Programmatically appeared first on Selenium Webdriver Appium Complete Tutorial.

For these failures there may be so many reasons. Will see some of them below:

1.Some of the elements may not load properly.
2.Due to some network slowness.
3.Functionality may got changed.
4.Locator value may got changed.. Etc…

Because of the reasons tests will fail. After completion of the execution if there are any failures, immediately we can not raise bugs. In the above scenarios failures due to 1,2 and 4 will not cause the bugs as this is because of loading elements and network slowness. But due to 3, we can raise the bugs.

But how we can come to know that the failures because of which reason. To get the confirmation we need to rerun the failed scripts to know the exact reason. Then how we can execute only failed tests?

To execute only failed tests we have provision in the TestNg. After completion of the suite execution; just refresh the project folder then you can find a folder called “test-output” and there you can find an xml file called “testng-failed.xml”. This xml file contains only failed test cases. So, we can execute this xml file to rerun the failed test again.

Below is the sample program:

import org.testng.Assert;
import org.testng.annotations.Test;

public class OnlyFailedTestExecution {
    @Test
    public void testOne() {
        Assert.assertTrue(true);
        System.out.println("Pass Test Case");
    }

    @Test
    public void testTwo() {
        Assert.assertTrue(false);
        System.out.println("Faile Test Case");
    }
}

Execute the above program using below testng.xml file:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name="Suite">
  <test name="Test">
    <classes>
      <class name="OnlyFailedTestExecution"/>
    </classes>
  </test>
</suite>

Once your execute the above xml file then we can find the below output:

Now we want to execute only failed tests. For this we will go to the test-output folder and will execute the testng-failed.xml. Then we can see the below output.

In the above output we can see that only failed test got executed. And it ignores the execution of passed tests.
This way we can execute the only failed tests in testNg.
Please watch You tube video for better understanding.

The post Executing Only Failed Tests in TestNG appeared first on Selenium Webdriver Appium Complete Tutorial.

Capture screenshot for failed tests in testNG will discuss about how to take a screenshot when a test case fails while executing the test suite. The screenshot will give the information about on which screen the script  got failed during the execution. Then we can easily identify the issue by looking into the screenshot.

To achieve this we need to write 2 utility classes. One is to take the screenshot and another is to listen to the test status result and take the screenshot accordingly. For this we need to use Listeners in the testNG. We need to implement the ITestListener from the testNG in order to get the status of the test case. If the test case is fail then it will track that information and then will take the screenshot using the screenshot utility.

Below will see how can we achieve this. For this, we need to write 4 different classes. One is MainTest which will be used to initiate the WebDriver as we need to use the same webdriver instance across our framework. So, whenever there is a need of using webdriver instance then that class will extend this MainTest. Then we can maintain a single webdriver instance across our project.

Second is GetScreenshot which will be used to take the screenshot when there is a need. This is not only useful for the failed tests. If you want to capture screenshot anywhere in the project then you can use this utility to take the screenshot. But here we are using this in the listener as we need to take the screenshot for the failed tests.

Third is ListenerTest which will be used to listen the status of our test cases and act accordingly. For this we need to implement ITestListener interface from the testNG. And we need to use this listener in the testng.xml file to track the test cases status. Once there is any failure in the test case then it will call the listener and we have to mention to take the screenshot for the failed test.

Here, we need to implement all the methods which are available in the ITestListener interface. And it is not mandatory to implement all the methods but atleast we need to mention those methods without any logic. Here the useful method is onTestFailure. And this method contains the logic to capture the screenshot.

Fourth is CaptureScreenshotTests which is the class contains actual test cases which we are going to execute. Once there is any failure then it will be tracked by the onTestFailure from the listener class and then it will take the screenshot for the same.

Below program is to initialize the webdriver:

package com.automationtesting.screenshot;

import org.openqa.selenium.WebDriver;

public class MainTest {
    public static WebDriver driver;
}

Below program is to capture the screenshot:

package com.automationtesting.screenshot;

import java.io.File;
import java.io.IOException;

import org.apache.commons.io.FileUtils;
import org.openqa.selenium.OutputType;
import org.openqa.selenium.TakesScreenshot;

public class GetScreenshot extends MainTest {
    public static String capture(String screenshotName) throws IOException {
        TakesScreenshot ts = (TakesScreenshot) driver;
        File source = ts.getScreenshotAs(OutputType.FILE);
        String dest = System.getProperty("user.dir") + "/ErrorScreenshot/" + screenshotName + ".png";
        File destination = new File(dest);
        FileUtils.copyFile(source, destination);

        return dest;
    }
}

Below program is to implement the listener:

package com.automationtesting.screenshot;

import java.io.IOException;

import org.testng.ITestContext;
import org.testng.ITestListener;
import org.testng.ITestResult;

public class ListenerTest extends MainTest implements ITestListener {

    @Override
    public void onTestStart(ITestResult result) {
        // TODO Auto-generated method stub

    }

    @Override
    public void onTestSuccess(ITestResult result) {
        // TODO Auto-generated method stub

    }

    @Override
    public void onTestFailure(ITestResult result) {
        try {
            GetScreenshot.capture(result.getName());
        } catch (IOException e) {
            // TODO Auto-generated catch block
            e.printStackTrace();
        }
    }

    @Override
    public void onTestSkipped(ITestResult result) {
        // TODO Auto-generated method stub

    }

    @Override
    public void onTestFailedButWithinSuccessPercentage(ITestResult result) {
        // TODO Auto-generated method stub

    }

    @Override
    public void onStart(ITestContext context) {
        // TODO Auto-generated method stub

    }

    @Override
    public void onFinish(ITestContext context) {
        // TODO Auto-generated method stub

    }
}

Below program is for actual test cases:

package com.automationtesting.screenshot;

import org.openqa.selenium.firefox.FirefoxDriver;
import org.testng.Assert;
import org.testng.annotations.Test;

public class CaptureScreenshotTests extends MainTest {

    @Test
    public void captureScreenshot() {
        System.setProperty("webdriver.firefox.marionette", "D:\\drivers\\geckodriver-0.10.0\\geckodriver.exe");
        driver = new FirefoxDriver();
        driver.get("https://automationtesting.in");
        String title = driver.getTitle();
        Assert.assertEquals("Home - Automation Test", title);
        driver.close();
    }
}

In the above program it will try to assert the page title. But we intentionally failing this assert to capture the screenshot for this failure.

Below program is to execute the test cases from testng.xml file:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name="Suite">
<listeners>
<listener class-name="com.automationtesting.screenshot.ListenerTest"></listener>
</listeners>
  <test name="Test">
    <classes>
      <class name="com.automationtesting.screenshot.CaptureScreenshot"/>
    </classes>
  </test>
</suite>

Once you execute the above xml file then it capture the screenshot and it will place that in the ErrorScreenshot folder with the method name  in the current project folder structure.
This way we can achieve this functionality.
Please watch You tube video for better understanding.

The post Capture Screenshot for Failed Tests in TestNG appeared first on Selenium Webdriver Appium Complete Tutorial.

We will write the test cases how we want to execute but by default testNG will not execute in order how we have written. For this we need to use priority attribute for each and every test to execute the test cases in predefined order. But writing priority for each test case is tedious as we may have so many test cases in our test suite.

To overcome this problem, there is one more option called “preserve-order”in the testNG. We can use this attribute at suite level or test level.  If you set this value to “true” then it will execute the tests which are mentioned in the order in testng,xml file. Means, it will now not execute the tests in alphabetical order.

The post Preserve Order in TestNG appeared first on Selenium Webdriver Appium Complete Tutorial.

In order to set the priority to the tests then we can use one of the @Test attributes called “Priority”. By default all the tests will have the same priority called Zero(i.e. If you not set any priority then it will take the priority as Zero).
If you give the priority equal to all the test cases then all the tests will execute in alphabetical order. Here we will see how the priority will work while executing the tests by taking few examples:
1. In the below example we will see test case execution flow without setting any priority to the tests (i.e. all the tests will have the priority as ZERO).

public class WithOutPriority
{
    @Test
    public void secondTest()
    {
        System.out.println("In secondTest method");
    }
    
    @Test
    public void thirdTest()
    {
        System.out.println("In thirdTest method");
    }
    
    @Test
    public void fourthTest()
    {
        System.out.println("In fourthTest method");
    }
}

Below is the Output for the same:

If we observe the above output of all the 3 methods they executed in the alphabetical order. We have the order in test class is secondTest, thirdTest and fourthTest. But after execution the output is fourthTest, secondTest and thirdTest.

2.In the below example we will see test case execution flow with Priority attribute. Will take three test methods and will set the priority to them like one is without priority attribute and remaining

with 1 and 2.

public class PartialPriority
{
    @Test(priority = 1)
    public void secondTest()
    {
        System.out.println("In secondTest method");
    }
    
    @Test
    public void thirdTest()
    {
        System.out.println("In thirdTest method");
    }
    
    @Test(priority = 2)
    public void fourthTest()
    {
        System.out.println("In fourthTest method");
    }
}

Below is the Output for the same:

If we observe the above output of all the 3 methods they executed as per the priorities we set. The test without priority executed first as the default priority is equal to ZERO and it takes the high priority. And then priority = 1 will execute and last priority = 2 will execute.

3.In the below example we will see test case execution flow with Priority attribute. Will take three test methods and will set the priority to them like 1,2 and 3

public class PriorityTest
{
    @Test(priority = 1)
    public void secondTest()
    {
        System.out.println("In secondTest method");
    }
    
    @Test(priority = 3)
    public void thirdTest()
    {
        System.out.println("In thirdTest method");
    }
    
    @Test(priority = 2)
    public void fourthTest()
    {
        System.out.println("In fourthTest method");
    }
}

Below is the Output for the same:

If we observe the above output of all the 3 methods they executed as per the priorities we set. The test with priority = 1 will execute first and priority = 2 will execute second and priority = 3 will execute last.
This way we can prioritize the tests in testNG to control the execution flow.
Please watch You tube video for better understanding.

The post Prioritizing Tests in TestNg appeared first on Selenium Webdriver Appium Complete Tutorial.

Sometimes we need to maintain separate test suite for smoke test and separate suite for sanity test and another for Regression testing. For ex, once you receive the new build then you can perform smoke test using its own xml file, same way you can perform sanity test also using its own xml file. But if you want to execute full regression then you need to include regression tests, smoke tests and sanity tests. In these kind of situation we will put all these three suite files into another xml file and then we can execute that single xml file to run all the test scripts available under these 3 suite files.
We will see this functionality with an example:
Let’s assume we have 3 packages called com.multiplesuite.regression, com.multiplesuite.smoke and com.multiplesuite.sanity and each package contains 2 class files and then each class will contain 1 test method.
Now we will write sample xml files for each and every package which we have discussed above:

1. Xml file for com.multiplesuite.regression (ex: regression.xml)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name="Suite">
  <test name="Test">
    <classes>
      <class name="com.multiplesuite.regression.regressionClassOne"/>
      <class name="com.multiplesuite.regression.regressionClassTwo"/>
    </classes>
  </test>
</suite>

In the above xml file it contains two classes called regressionClassOne and regressionClassTwo and each class contains its own methods.

2. Xml file for com.multiplesuite.smoke (ex: smoke.xml)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name="Suite">
  <test name="Test">
    <classes>
      <class name="com.multiplesuite.smoke.smokeClassOne"/>
      <class name="com.multiplesuite.smoke.smokeClassTwo"/>
    </classes>
  </test>
</suite>

In the above xml file it contains two classes called smokeClassOne and smokeClassTwo and each class contains its own methods.

3. Xml file for com.multiplesuite.sanity (ex: sanity.xml)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name="Suite">
  <test name="Test">
    <classes>
      <class name="com.multiplesuite.sanity.sanityClassTwo"/>
      <class name="com.multiplesuite.sanity.sanityClassOne"/>
    </classes>
  </test>
</suite>

In the above xml file it contains two classes called sanityClassOne and sanityClassTwo and each class contains its own methods.
If you want to execute only regression test then you can use regression.xml file to execute its specific tests and the same way we can do it for smoke test and sanity test also.
But now we want to execute all the above three xml files at a time. Then you need to put these three xml file into another xml and then run the same to achieve our requirement.
Below is the sample xml file to execute above 3 suite files: (ex: testng.xml)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name="MultipleSuite">
<suite-files>
    <suite-file path="regression.xml"></suite-file>
    <suite-file path="smoke.xml"></suite-file>
    <suite-file path="sanity.xml"></suite-file>
</suite-files>
</suite>

In the above file we can observe new tags called suite-files and suite-file-path. By using suite-file-path we can mention the individual suite files and can execute the same like run as testng suite.
This way we can execute multiple suite files from other xml file.
Please watch the you tube video for better understanding.

The post Execute Multiple XML files in TestNG appeared first on Selenium Webdriver Appium Complete Tutorial.

To generate custom reports in testng we need to use Reporters. To implement reporters, need to implement the IReporter interface in your class. These classes are called when the whole suite run ends. The object containing the information of the whole test run is passed to this class when called.
For this we need to have at least 2 classes. One is for actual test cases and other is for to implement the IReporter.
Below is the sample program for test cases class:

import org.testng.Assert;
import org.testng.annotations.Test;

public class loggerTest {
    @Test
    public void testOne() {
        Assert.assertTrue(true);
    }

    @Test
    public void testTwo() {
        Assert.assertTrue(false);
    }

    @Test(dependsOnMethods = { "testTwo" })
    public void testThree() {
        Assert.assertTrue(true);
    }
}

When you execute the above program, the status of the test cases should be listen by the listener class. We have three methods called testOne, testTwo and testThree in the above program one is to pass and second is to fail and third is to skip status. After execution of the suits, the listener will track the status of the each test.
Below is the sample listener class which will implements the IReporter

import java.util.List;
import java.util.Map;
import org.testng.IReporter;
import org.testng.ISuite;
import org.testng.ISuiteResult;
import org.testng.ITestContext;
import org.testng.xml.XmlSuite;

public class CustomReporter implements IReporter {
    @Override
    public void generateReport(List<XmlSuite> xmlSuites, List<ISuite> suites, String outputDirectory) {
        // Iterating over each suite included in the test
        for (ISuite suite : suites) {
            // Following code gets the suite name
            String suiteName = suite.getName();
            // Getting the results for the said suite
            Map<String, ISuiteResult> suiteResults = suite.getResults();
            for (ISuiteResult sr : suiteResults.values()) {
                ITestContext tc = sr.getTestContext();
                System.out.println(
                        "Passed tests for suite '" + suiteName + "' is:" + tc.getPassedTests().getAllResults().size());
                System.out.println(
                        "Failed tests for suite '" + suiteName + "' is:" + tc.getFailedTests().getAllResults().size());
                System.out.println("Skipped tests for suite '" + suiteName + "' is:"
                        + tc.getSkippedTests().getAllResults().size());
            }
        }
    }
}

The above class implements the IReporter. So, it has to implement all the methods which are available in that interface. And it is not mandatory to use all the methods, we can left blank some of the methods which are not relevant to the requirement.
Now we have to create a testng.xml file to execute the above tests and it should have a mandatory tag called listener. It will call the listener class to listen the status of the each and every test which will execute.
Below is the sample program to execute the above program:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name="Suite">
<listeners>
<listener class-name="CustomReporter"></listener>
</listeners>
  <test name="Test">
    <classes>
      <class name="loggerTest"/>
    </classes>
  </test>
</suite>

Output for the above program is:

This way we can use custom listeners to generate the reports after execution.
Please watch the you tube video for better understanding.

The post Custom Reporter in TestNG appeared first on Selenium Webdriver Appium Complete Tutorial.

To generate custom loggers in testng we need to use Listeners. To implement listeners, need to implement the ITestListener interface in your class. These classes are notified at runtime by TestNG when the test case executes.
For this we need to have at least 2 classes. One is for actual test cases and other is for to implement the ITestListener.
Below is the sample program for test cases class:

import org.testng.Assert;
import org.testng.annotations.Test;

public class loggerTest
{
    @Test
    public void testOne()
    {
        Assert.assertTrue(true);
    }
    
    @Test
    public void testTwo()
    {
        Assert.assertTrue(false);
    }
}

When you execute the above program, the status of the test cases should be listen by the listener class. We have two methods called testOne and testTwo in the above program one is to pass and second is to fail status. While executing the tests, the listener will track the status of the each test..
Below is the sample listener class which will implements the ITestListener

import org.testng.ITestContext;
import org.testng.ITestListener;
import org.testng.ITestResult;

public class listenerTest implements ITestListener {

    // It executes for on each test Start
    @Override
    public void onTestStart(ITestResult result) {
        System.out.println("Test Method Started :" + result.getName());
    }

    // It executes for only Passed tests
    @Override
    public void onTestSuccess(ITestResult result) {
        System.out.println("Test Method Passed :" + result.getName());
    }

    // It executes for only Failed tests
    @Override
    public void onTestFailure(ITestResult result) {
        System.out.println("Test Method Failed :" + result.getName());
    }

    // It executes for only Skipped tests
    @Override
    public void onTestSkipped(ITestResult result) {
        System.out.println("Test Method Skipped :" + result.getName());
    }

    @Override
    public void onTestFailedButWithinSuccessPercentage(ITestResult result) {
        // No need to implement all the methods. Can leave empty.
    }

    // It executes for on Suite start
    @Override
    public void onStart(ITestContext context) {
        System.out.println("Test on Start :" + context.getName());
    }

    // It executes for on Suite finish
    @Override
    public void onFinish(ITestContext context) {
        System.out.println("Test on Finish :" + context.getName());
    }
}

The above class implements the ITestListener. So, it has to implement all the methods which are available in that interface. And it is not mandatory to use all the methods, we can left blank some of the methods which are not relevant to the requirement.
Now we have to create a testng.xml file to execute the above tests and it should have a mandatory tag called listener. It will call the listener class to listen the status of the each and every test which will execute.
Below is the sample program to execute the above program:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name="Suite">
<listeners>
<listener class-name="listenerTest"></listener>
</listeners>
  <test name="Test">
    <classes>
      <class name="loggerTest"/>
    </classes>
  </test>
</suite>

Output for the above program is:

This way we can use custom listeners to log the messages while executing.
Please watch the you tube video for better understanding.

The post Custom Logger in TestNG appeared first on Selenium Webdriver Appium Complete Tutorial.

test execution of the said test and mark it as failing.

TestNG supports assertion of a test using the Assert class which is part of the testNG library. The following table describes few of the methods and their usage that are available with the Assert class in testng:

Frequently Used Assertions:

In the above table we have seen some of the assertions which are very frequently used. If the condition meets as expected then the assert passed otherwise it will fails the test and stops the execution of that test.

Below is the sample program where all the assertions will PASS:

import org.testng.Assert;
import org.testng.annotations.Test;
public class PassedAssertions
{
    @Test
    public void testOne()
    {
        Assert.assertTrue(true, "Assert Failed as the actual condition is False");
    }
    @Test
    public void testTwo()
    {
        Assert.assertFalse(false, "Assert Failed as the actual condition is True");
    }
    
    @Test
    public void testThree()
    {
        String s = "Krishna";
        Assert.assertNotNull(s,"Assert Failed as the String is Null");
    }
    
    @Test
    public void testFour()
    {
        String s = null;
        Assert.assertNull(s, "Assert Failed as the String is NOT NULL");
    }
    
    @Test
    public void testFive()
    {
        String s1 = "Krishna";
        String s2 = "Krishna";
        Assert.assertEquals(s1, s2, "Assert Failed as the two string are NOT EQUAL");
    }
    
    @Test
    public void testSix()
    {
        String s1 = "Krishna";
        String s2 = "Sakinala";
        Assert.assertNotEquals(s1, s2, "Assert Failed as the two string are EQUAL");
    }
}

Below is the output for the above Program:

Below is the sample program where all the assertions will FAIL:

import org.testng.Assert;
import org.testng.annotations.Test;


public class FailedAssertions
{
    @Test
    public void testOne()
    {
        Assert.assertTrue(false, "Assert Failed as the actual condition is False");
    }
    @Test
    public void testTwo()
    {
        Assert.assertFalse(true, "Assert Failed as the actual condition is True");
    }
    
    @Test
    public void testThree()
    {
        String s = null;
        Assert.assertNotNull(s,"Assert Failed as the String is Null");
    }
    
    @Test
    public void testFour()
    {
        String s = "Krishna";
        Assert.assertNull(s, "Assert Failed as the String is NOT NULL");
    }
    
    @Test
    public void testFive()
    {
        String s1 = "Krishna";
        String s2 = "Sakinala";
        Assert.assertEquals(s1, s2, "Assert Failed as the two string are NOT EQUAL");
    }
    
    @Test
    public void testSix()
    {
        String s1 = "Krishna";
        String s2 = "Krishna";
        Assert.assertNotEquals(s1, s2, "Assert Failed as the two string are EQUAL");
    }
}

Below is the output for the above Program:

This way we will use the Assertions in testNG to know the status of the tests which are executed.

Please watch the you tube video for better understanding.

The post TestNG Assertions appeared first on Selenium Webdriver Appium Complete Tutorial.