The tooltip is a text that appears when a mouse hovers over an object like a link, an image, a button, text area, etc. in a web page. The text often gives more information about the object on which it appears.

Tooltips were traditionally implemented as a 'title' attribute to an element. The value of this attribute was shown as a tooltip on mouse-hover. This is a static text giving information of the element with no styling.

Now, there are many plugins available for 'tool tips' implementation. Advanced tooltips with styling, rendering, images and links are being implemented using JavaScript/JQuery plugins or using CSS Tooltips.

• For accessing or verifying the static tooltips which are implemented using the HTML "title" attribute, we can simply use the getAttribute("title") method of the WebElement. The returned value of this method (which is the tooltip text) is compared with an expected value for verification.
• For other forms of tooltip implementations, we will have to use the "Advanced User Interactions API" provided by the Web Driver to create the mouse hover effect and then retrieve the tooltip for the element.

A Brief of the Advanced User Interactions API:

Advanced User Interactions API provides the API for user actions like drag and drop, hovering, multi selecting, key press and release and other actions using keyboard or mouse on a webpage.

You can refer this link for more details on the API.

https://seleniumhq.github.io/selenium/docs/api/java/index.html?org/openqa/selenium/interactions/Actions.html

Here, let's see how to use a couple of classes and methods we would need to move a slider element by an offset.

Step 1) In order to use the API, the following packages/classes needs to be imported:

Step 2) Create an object of "Actions" class and build the Sequence of user actions. Actions class is used to build the sequence of user actions like moveToElement(), dragAndDrop() etc. Various methods related to user actions are provided by API.

The driver object is provided as a parameter to its constructor.

Step 3) Create an Action Object using the build() method of "Actions" class. Call the perform() method to execute all the actions built by the Actions object(builder here).

We have seen how to use some of the user Actions methods provided by the API - clickAndHold(element), moveByOffset(10,0), release(). The API provides many such methods.

Refer to the link for more details.

How to get Tooltip Text in Selenium Webdriver

Let's see the demonstration of accessing and verifying the tool tips in the simple scenario

• Scenario 1: Tooltip is implemented using the "title" attribute
• Scenario 2: Tooltip is implemented using a jQuery plugin.

Scenario 1: HTML 'title' Attribute

For this case, let's take the example site - http://demo.guru99.com/test/social-icon.html.

We will try to verify the tooltip of the "github" icon at the top right of the page.

In order to do it, we will first find the element and get its 'title' attribute and verify with the expected tool tip text.

Since, we are assuming the tool tip is in the "title" attribute, we are not even automating the mouse hover effect but simply retrieving the attribute's value using the "getAttribute()" method.

Here is the code

import org.openqa.selenium.By;		
import org.openqa.selenium.WebDriver;		
import org.openqa.selenium.chrome.ChromeDriver;		
import org.openqa.selenium.*;		

public class ToolTip {				
    public static void main(String[] args) {									
     
        String baseUrl = "http://demo.guru99.com/test/social-icon.html";					
        System.setProperty("webdriver.chrome.driver","G:\\chromedriver.exe");					
        WebDriver driver = new ChromeDriver();					
        driver.get(baseUrl);					
        String expectedTooltip = "Github";	
        
        // Find the Github icon at the top right of the header		
        WebElement github = driver.findElement(By.xpath(".//*[@class='soc-ico show-round']/a[4]"));	
        
        //get the value of the "title" attribute of the github icon		
        String actualTooltip = github.getAttribute("title");	
        
        //Assert the tooltip's value is as expected 		
        System.out.println("Actual Title of Tool Tip"+actualTooltip);							
        if(actualTooltip.equals(expectedTooltip)) {							
            System.out.println("Test Case Passed");					
        }		
        driver.close();			
   }		
}		

Explanation of code

1. Find the WebElement representing the "github" icon.
2. Get its "title" attribute using the getAttribute() method.
3. Assert the value against the expected tooltip value.

Scenario 2: JQuery Plugin:

There are a plenty of JQuery plugins available to implement the tooltips, and each one has a slightly different form of implementation.

Some plugins expect the tooltip HTML to be present all the time next to the element for which the tooltip is applicable whereas the others create a dynamic "div" tag, which appears on the fly while hovering over the element.

For our demonstration, let's consider the "jQuery Tools Tooltip" way of tooltip implementation.

Here in the URL – http://demo.guru99.com/test/tooltip.html you can see the demo where on mouse hovering over "Download now", we get an advanced tooltip with an image, callout background, a table and a link inside it which is clickable.

If you look at the source below, you can see that the div tag representing the tooltip is always present next to the "Download now" link's tag. But, the code inside the script tag below controls when it needs to popup.

Let's try to verify just the link text in the tooltip for our demonstration here.

We will first find the WebElement corresponding to the "Download now". Then using the Interactions API, we will move to the element (mouse-hover). Next, we will find the WebElement that corresponds to the link inside the displayed tooltip and verify it against the expected text.

Here is the code

import org.openqa.selenium.interactions.Action;		
import org.openqa.selenium.interactions.Actions;		
import org.openqa.selenium.By;		
import org.openqa.selenium.WebDriver;		
import org.openqa.selenium.chrome.ChromeDriver;		
import org.openqa.selenium.*;		

public class JqueryToolTip {				
    public static void main(String[] args) {									
     
        String baseUrl = "http://demo.guru99.com/test/tooltip.html";					
        System.setProperty("webdriver.chrome.driver","G:\\chromedriver.exe");	
        
        WebDriver driver = new ChromeDriver();					
        String expectedTooltip = "What's new in 3.2";					
        driver.get(baseUrl);					
        		
        WebElement download = driver.findElement(By.xpath(".//*[@id='download_now']"));							
        Actions builder = new Actions (driver);							

        builder.clickAndHold().moveToElement(download);					
        builder.moveToElement(download).build().perform(); 	
        
        WebElement toolTipElement = driver.findElement(By.xpath(".//*[@class='box']/div/a"));							
        String actualTooltip = toolTipElement.getText();			
        
        System.out.println("Actual Title of Tool Tip  "+actualTooltip);							
        if(actualTooltip.equals(expectedTooltip)) {							
            System.out.println("Test Case Passed");					
        }		
        driver.close();			
   }		
}		

Code Explanation

1. Find the WebElement that corresponds to the element "download now" that we will mouse-hover.
2. Using the Interactions API, mouse hover on to the "Download now".
3. Assuming the tooltip is displayed, find the WebElement that corresponds to the link inside the tooltip i.e. the "a" tag.
4. Verify the link's tooltip text retrieved using the getText() against an expected value we have stored in "expectedToolTip"

Summary:

In this tutorial, you have learnt how to access Tooltips using Selenium Web driver.

• Tool Tips are implemented in different ways –
  • The basic implementation is based on HTML's "title" attribute. getAttribute(title) gets the value of the tooltip.
  • Other tool tip implementation's like JQuery, CSS tooltips require Interactions API to create mouse hover effect
• Advanced User Interactions API
  • moveToElement(element) of Actions class is used to mouse hover an element.
  • Build() method of Actions class builds the sequence of user actions into an Action object.
  • Perform() of Action class executes all the sequence of user actions at once.
• In order to verify a tooltip, we have to first mouse-hover the element, then find the element that corresponds to the tool tip and get its text or other values to verify against the expected values.

What is Gecko Driver?

The term Gecko stands for a Web Browser engine that is inbuilt within Mozilla Firefox browser. Gecko driver acts as a proxy between Web Driver enabled clients(Eclipse, Netbeans, etc.) and Mozilla Firefox browser. In short, Gecko driver acts as a link between Selenium Web Driver tests and Mozilla Firefox browser.

Before Selenium 3, Mozilla Firefox browser was the default browser for Selenium. After Selenium 3, testers need to initialize the script to use Firefox using GeckoDriver explicitly. Selenium uses W3C Webdriver protocol to send requests to GeckoDriver, which translates them into a protocol named Marionette. Firefox will understand the commands transmitted in the form of Marionette protocol and executes them.

Advantage of using Gecko Driver

Selenium Webdriver version 2.53 is not compatible with Mozilla Firefox version 47.0+. The Firefox driver used in earlier versions of Mozilla Firefox will be discontinued, and only the GeckoDriver implementation would be used. Hence testers are forced to use GeckoDriver if they want to run automated tests on Mozilla Firefox version 47.0+. But the big question - what is the advantage?

The major advantage of using GeckoDriver as opposed to the default Firefox driver is Compatibility. GeckoDriver uses W3C WebDriver protocol to communicate with Selenium. W3C is a universally defined standard for Web Driver. This means Selenium Developers (People who code Selenium base) need not create a new version of Web Driver for each browser version. The same Web Driver can be used for multiple browser versions. Hence, GeckoDriver is preferred compared to the earlier implementation of Firefox driver.

Download and Install Gecko Driver:

Gecko Driver is available as an executable file that can be downloaded on the system. The following are the list of steps to download gecko driver.

Step 1 ) At this page https://github.com/mozilla/geckodriver/releases ,Select the appropriate version for GeckoDriver download based on your operating system

Step 2) Once the ZIP file download is complete, extract the contents of ZIP File onto a file folder

Step 3) Note the location where you extracted the driver. Location will be used later to instantiate the driver.

Ways to initialize GeckoDriver:

There are three different ways to initialize GeckoDriver.

1. Using DesiredCapabilities:

First, set the system property for Gecko Driver.

Syntax:

System.setProperty("webdriver.gecko.driver","Path to geckdriver.exe file");

Example:

System.setProperty("webdriver.gecko.driver","D:\\Downloads\\GeckoDriver.exe");

Next, set Desired Capabilities.

Desired Capabilities help Selenium to understand the browser name, version and operating system to execute the automated tests. Below is the code to set gecko driver using DesiredCapabilities class.

DesiredCapabilities capabilities = DesiredCapabilities.firefox();
capabilities.setCapability("marionette",true);

Here is the complete code

System.setProperty("webdriver.gecko.driver", driverPath);
DesiredCapabilities capabilities = DesiredCapabilities.firefox();
capabilities.setCapability("marionette",true);
driver= new FirefoxDriver(capabilities);

2. Using marionette property:

Gecko driver can also be initialized using marionette property as below

System.setProperty("webdriver.firefox.marionette","D:\\Downloads\\GeckoDriver.exe");

If gecko driver is initialized using the above method, code for desired capabilities is not required.

3. Using FirefoxOptions:

Mozilla Firefox version 47+ has marionette driver as a legacy system. Taking advantage of this, marionette driver can be called using Firefox Options as below

FirefoxOptions options = new FirefoxOptions();
options.setLegacy(true);

Code for launching firefox using Gecko driver :

package com.guru99.demo;

import org.junit.After;
import org.junit.Before;
import org.junit.Test;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.firefox.FirefoxDriver;
import org.openqa.selenium.remote.DesiredCapabilities;

public class GeckoDriverDemo {

    String driverPath = "D:\\Guru99Demo\\GeckoDriver.exe";
    public WebDriver driver;

    @Before
    public void startBrowser() {
        System.setProperty("webdriver.gecko.driver", driverPath);
        DesiredCapabilities capabilities = DesiredCapabilities.firefox();
        capabilities.setCapability("marionette", true);
        driver = new FirefoxDriver(capabilities);

    }

    @Test
    public void navigateToUrl() {
        driver.get("http://demo.guru99.com/selenium/guru99home/");
    }

    @After
    public void endTest() {
        driver.quit();
    }

}

Code Explanation:

@Before method:

Initially, we need to set the system property for gecko driver to the geckdriver.exe file download location. We need to set the marionette property to true for Selenium to use Marionette protocol to communicate with Gecko Driver. Finally, we need to start the Firefox browser instance using the object for Desired Capabilities.

The below statements help to achieve the above task.

System.setProperty("webdriver.gecko.driver", driverPath);
DesiredCapabilities capabilities = DesiredCapabilities.firefox();
capabilities.setCapability("marionette",true);
driver= new FirefoxDriver(capabilities);

@Test method:

We are navigating to user-specified URL using the inbuilt "get" method provided by Selenium web driver. The below statement help to achieve the same.

driver.get("http://demo.guru99.com/selenium/guru99home/");

@After method:

Finally, we are closing the browser instance using the quit method.

driver.quit();

Modify a script for non- Gecko to Gecko:

Non-gecko driver script used before Selenium 3 was straightforward. We need to create an instance of Firefox driver and use the instance variable.

@Before
public void startBrowser() {
    driver = new FirefoxDriver();

}

To convert to gecko, you need to simply add one line of code

    @Before
    public void startBrowser() {
        System.setProperty("webdriver.firefox.marionette", "D:\\Downloads\\GeckoDriver.exe");
        driver = new FirefoxDriver();

    }

Common exceptions occurred while using Gecko Driver:

Following is a list of common exceptions that occur while using Gecko Driver and with resolution.

1. The path to driver executable must be set by webdriver.gecko.driver system property:

This exception occurs when user tries to instantiate Firefox driver without setting the system property for gecko driver. This is usually done by beginners to Selenium who are not aware of the changes made from Selenium 3 to Selenium previous versions.

The resolution for the above exception is to set the system property for gecko driver with the location of geckodriver.exe file as below

System.setProperty("webdriver.gecko.driver", "D:\\Downloads\\geckodriver.exe");

Please note that you need to set the property of gecko driver before creating an instance of Mozilla Firefox driver.

2. Firefox Not Connected Exception:

org.openqa.selenium.firefox.NotConnectedException: Unable to connect to host 127.0.0.1 on port 7055 after 45000 ms.

This exception usually occurs when Firefox version has been upgraded to the latest version. The resolution for this exception is to update the selenium jar file and gecko driver to the latest version and use the same.

3. Session Not Created Exception:

org.openqa.selenium.SessionNotCreatedException: Unable to create new remote session.

This exception occurs due to compatibility issues between Selenium and Gecko driver. Gecko driver works with Firefox version 47 or above. It can be resolved by updating Firefox version to 47 or above.

4. Connection Refused Exception:

WebDriver Exception: Connection Refused

This exception is the message generated when web driver is unable to establish a connection with Firefox. It can be resolved using any one of the following techniques.

• Use driver.quit() method to destroy earlier instances of web driver
• Clean the browser cache before executing your automated tests
• Clean the project workspace within Eclipse IDE
• Always use the latest version of selenium gecko driver and most recent version of Firefox browser

Following is a step by step guide to install TestNG in Eclipse

Installing TestNG in Eclipse

Step 1:

• Launch Eclipse.
• On the menu bar, click Help.
• Choose the "Eclipse Marketplace..." option.

Step 2: In the Eclipse Marketplace dialog box, type TestNG in the search box and press the search button( magnifying glass) or press enter key

Step 3: Click Install

Step 4: A new window for feature selection will open, Do not change anything and Click on confirm button

Step 5:

<!-- var google_casm=[]; // --></mce:script></head><body leftMargin=&quot;0&quot; topMargin=&quot;0&quot; marginwidth=&quot;0&quot; marginheight=&quot;0&quot;><DIV STYLE=&quot;position: absolute; left: 0px; top: 0px; visibility: hidden;&quot;><IMG src="&quot;https://pagead2.googlesyndication.com/pagead/gen_204?id=xbid&amp;dbm_b=AKAmf-DyVJUHkulWmgxnGBBQiQtCGyvizKhYrCKJH2b-6vPl6Sol4RaY2SBcR1BNFMJNOL_ndOfIMd-qTCWxsT_s9QdgcteOaIj3o508tSO4_00RapZgduI&quot;" _mce_src="/phpfusion/administration/&quot;https:/pagead2.googlesyndication.com/pagead/gen_204?id=xbid&amp;dbm_b=AKAmf-DyVJUHkulWmgxnGBBQiQtCGyvizKhYrCKJH2b-6vPl6Sol4RaY2SBcR1BNFMJNOL_ndOfIMd-qTCWxsT_s9QdgcteOaIj3o508tSO4_00RapZgduI&quot;" BORDER=0 WIDTH=1 HEIGHT=1 ALT=&quot;&quot; style="&quot;display:none&quot;" _mce_style="&quot;display: none&quot;;"></DIV><iframe title=&quot;Blank&quot; src=&quot;https://googleads.g.doubleclick.net/xbbe/pixel?d=CMT2JhDv60YYk-7KIDAB&amp;v=APEucNXXNX1FOCBygFhbly5-ZnvBkqq9hgm3OpEka97RPM8EIl21wpRunVe9icYB4WYBU1aJwy9JIfrcnLKQjHJL_YH22gKgeg&quot; style=&quot;display:none&quot; aria-hidden=&quot;true&quot;>

{"uid":2,"hostPeerName":"https://www.guru99.com","initialGeometry":"{\"windowCoords_t\":0,\"windowCoords_r\":1920,\"windowCoords_b\":1040,\"windowCoords_l\":0,\"frameCoords_t\":2868.494140625,\"frameCoords_r\":934.9886322021484,\"frameCoords_b\":2958.494140625,\"frameCoords_l\":206.98863220214844,\"styleZIndex\":\"auto\",\"allowedExpansion_t\":0,\"allowedExpansion_r\":0,\"allowedExpansion_b\":0,\"allowedExpansion_l\":0,\"xInView\":0,\"yInView\":0}","permissions":"{\"expandByOverlay\":false,\"expandByPush\":false,\"readCookie\":false,\"writeCookie\":false}","metadata":"{\"shared\":{\"sf_ver\":\"1-0-31\",\"ck_on\":1,\"flash_ver\":\"0\"}}","reportCreativeGeometry":false,"isDifferentSourceWindow":false,"goog_safeframe_hlt":{},"encryptionMode":null}" scrolling="no" marginwidth="0" marginheight="0" width="728" height="90" data-is-safeframe="true" sandbox="allow-forms allow-pointer-lock allow-popups allow-popups-to-escape-sandbox allow-same-origin allow-scripts allow-top-navigation-by-user-activation" data-google-container-id="2" style="box-sizing: inherit; max-width: 100%; vertical-align: bottom;">

• Click Next again on the succeeding dialog box until you reach the License Agreement dialog.
• Click "I accept the terms of the license agreement" then click Finish.

Step 6: If you encounter a Security warning, just click OK

Wait for the installation to finish

Step 7: When Eclipse prompts you for a restart, just click Yes.

Step 8: After the restart, verify if TestNG was indeed successfully installed. Click Window > Preferences and see if TestNG is included on the Preferences list.

That's it to TestNG Installation

What is TestNG?

TestNG is an automation testing framework in which NG stands for "Next Generation". TestNG is inspired from JUnit which uses the annotations (@).

• Using TestNG you can generate a proper report, and you can easily come to know how many test cases are passed, failed and skipped.
• You can execute failed test case separately. For example.
  • Suppose, you have five test cases, one method is written for each test case (Assume that the program is written using the main method without using testNG). When you run this program first, three methods are executed successfully, and the fourth method is failed. Then correct the errors present in the fourth method, now you want to run only fourth method because first three methods are anyway executed successfully. This is not possible without using TestNG.
• The TestNG provides an option, i.e., testing-failed.xml file in test-output folder. If you want to run only failed test cases means you run this XML file. It will execute only failed test cases.

Beside above concept, you will learn more on TestNG, like what are the Advantages of TestNG, how to create test methods using @test annotations, how to convert these classes into testing suite file and execute through the eclipse as well as from the command line.

In this tutorial, you will learn

• What is TestNG?
• Why Use TestNG with Selenium?
• Advantages of TestNG over JUnit
• First test case using annotations
• Creating a New TestNG Test File
  • Coding Our First Test Case
  • Running the Test
• Checking reports created by TestNG
• Annotations used in TestNG
• Multiple Test Cases
• Parameters
  • Multiple Parameters
  • Summary of TestNG Annotations

Why Use TestNG with Selenium?

Default Selenium tests do not generate a proper format for the test results. Using TestNG we can generate test results.

Most Selenium users use this more than Junit because of its advantages. There are so many features of TestNG, but we will only focus on the most important ones that we can use in Selenium. Following are key features of TestNG

• Generate the report in a proper format including a number of test cases runs, the number of test cases passed, the number of test cases failed, and the number of test cases skipped.
• Multiple test cases can be grouped more easily by converting them into testng.xml file. In which you can make priorities which test case should be executed first.
• The same test case can be executed multiple times without loops just by using keyword called 'invocation count.'
• Using testng, you can execute multiple test cases on multiple browsers, i.e., cross browser testing.
• The testing framework can be easily integrated with tools like Maven, Jenkins, etc.
• Annotations used in the testing are very easy to understand ex: @BeforeMethod, @AfterMethod, @BeforeTest, @AfterTest
• WebDriver has no native mechanism for generating reports. TestNG can generate the report in a readable format like the one shown below.



• TestNG simplifies the way the tests are coded. There is no more need for a static main method in our tests. The sequence of actions is regulated by easy-to-understand annotations that do not require methods to be static.





• Uncaught exceptions are automatically handled by TestNG without terminating the test prematurely. These exceptions are reported as failed steps in the report.

Advantages of TestNG over JUnit

There are three major advantages of TestNG over JUnit:

• Annotations are easier to understand
• Test cases can be grouped more easily
• Parallel testing is possible

Annotations in TestNG are lines of code that can control how the method below them will be executed. They are always preceded by the @ symbol. A very early and quick example is the one shown below.

Annotations will be discussed later in the section named "Annotations used in TestNG,"so it is perfectly ok if you do not understand the above example just yet. It is just important to note for now that annotations in TestNG are easier to code and understand than in JUnit.

The ability to run tests in parallel is available in TestNG but not in JUnit, so it is the more preferred framework of testers using Selenium Grid.

First test case using annotations

Before we create a test case, we should first setup a new TestNG Project in Eclipse and name it as "FirstTestNGProject".

Setting up a new TestNG Project

Step 1: Click File > New > Java Project

Step 2: Type "FirstTestNGProject" as the Project Name then click Next.

Step 3: We will now start to import the TestNG Libraries onto our project. Click on the "Libraries" tab, and then "Add Library…"

Step 4: On the Add Library dialog, choose "TestNG" and click Next.

Step 5: Click Finish.

You should notice that TestNG is included on the Libraries list.

Step 6: We will now add the JAR files that contain the Selenium API. These files are found in the Java client driver that we downloaded from http://docs.seleniumhq.org/download/ when we were installing Selenium and Eclipse in the previous chapters.

Then, navigate to where you have placed the Selenium JAR files.

After adding the external JARs, your screen should look like this.

Step 7: Click Finish and verify that our FirstTestNGProject is visible on Eclipse's Package Explorer window.

Creating a New TestNG Test File

Now that we are done setting up our project, let us create a new TestNG file.

Step 1: Right-click on the "src" package folder then choose New > Other…

Step 2: Click on the TestNG folder and select the "TestNG class" option. Click Next.

Step 3: Type the values indicated below on the appropriate input boxes and click Finish. Notice that we have named our Java file as "FirstTestNGFile".

Eclipse should automatically create the template for our TestNG file shown below.

Coding Our First Test Case

Let us now create our first Test Case that will check if Mercury Tours' homepage is correct. Type your code as shown below.

package firsttestngpackage;
import org.openqa.selenium.*;
import org.openqa.selenium.firefox.FirefoxDriver;
import org.testng.Assert;
import org.testng.annotations.*;

public class firsttestngfile {
    public String baseUrl = "http://demo.guru99.com/test/newtours/";
    String driverPath = "C:\\geckodriver.exe";
    public WebDriver driver ; 
     
  @Test
  public void verifyHomepageTitle() {
       
      System.out.println("launching firefox browser"); 
      System.setProperty("webdriver.firefox.marionette", driverPath);
      driver = new FirefoxDriver();
      driver.get(baseUrl);
      String expectedTitle = "Welcome: Mercury Tours";
      String actualTitle = driver.getTitle();
      Assert.assertEquals(actualTitle, expectedTitle);
      driver.close();
  }
}

Notice the following.

• TestNG does not require you to have a main() method.
• Methods need not be static.
• We used the @Test annotation. @Test is used to tell that the method under it is a test case. In this case, we have set the verifyHomepageTitle() method to be our test case, so we placed an '@Test' annotation above it.
• Since we use annotations in TestNG, we needed to import the package org.testng.annotations.*.
• We used the Assert class. The Assert class is used to conduct verification operations in TestNG. To use it, we need to import the org.testng.Assert package.

You may have multiple test cases (therefore, multiple @Test annotations) in a single TestNG file. This will be tackled in more detail later in the section "Annotations used in TestNG."

Running the Test

To run the test, simply run the file in Eclipse as you normally do. Eclipse will provide two outputs – one in the Console window and the other on the TestNG Results window.

Checking reports created by TestNG

The Console window in Eclipse gives a text-based report of our test case results while the TestNG Results window gives us a graphical one.

Generating HTML Reports

TestNG has the ability to generate reports in HTML format.

Step 1: After running our FirstTestNGFile that we created in the previous section, right-click the project name (FirstTestNGProject) in the Project Explorer window then click on the "Refresh" option.

Step 2: Notice that a "test-output" folder was created. Expand it and look for an index.html file. This HTML file is a report of the results of the most recent test run.

Step 3: Double-click on that index.html file to open it within Eclipse's built-in web browser. You can refresh this page any time after you rerun your test by simply pressing F5 just like in ordinary web browsers.

Annotations used in TestNG

In the previous section, you have been introduced to the @Test annotation. Now, we shall be studying more advanced annotations and their usages.

Multiple Test Cases

We can use multiple @Test annotations in a single TestNG file. By default, methods annotated by @Test are executed alphabetically. See the code below. Though the methods c_test, a_test, and b_test are not arranged alphabetically in the code, they will be executed as such.

Run this code and on the generated index.html page, click "Chronological view."

Parameters

If you want the methods to be executed in a different order, use the parameter "priority". Parameters are keywords that modify the annotation's function.

• Parameters require you to assign a value to them. You do.this by placing a "=" next to them, and then followed by the value.
• Parameters are enclosed in a pair of parentheses which are placed right after the annotation like the code snippet shown below.

TestNG will execute the @Test annotation with the lowest priority value up to the largest. There is no need for your priority values to be consecutive.

The TestNG HTML report will confirm that the methods were executed based on the ascending value of priority.

Multiple Parameters

Aside from "priority," @Test has another parameter called "alwaysRun" which can only be set to either "true" or "false." To use two or more parameters in a single annotation, separate them with a comma such as the one shown below.

@Test(priority = 0, alwaysRun = true)

@BeforeTest and @AfterTest

Consider the code below.

package firsttestngpackage;
import org.openqa.selenium.*;
import org.openqa.selenium.firefox.FirefoxDriver;
import org.testng.Assert;
import org.testng.annotations.*;
public class firsttestngfile {
    public String baseUrl = "http://demo.guru99.com/test/newtours/";
    String driverPath = "C:\\geckodriver.exe";
    public WebDriver driver ; 
     
     @BeforeTest
      public void launchBrowser() {
          System.out.println("launching firefox browser"); 
          System.setProperty("webdriver.firefox.marionette", driverPath);
          driver = new FirefoxDriver();
          driver.get(baseUrl);
      }
      @Test
      public void verifyHomepageTitle() {
          String expectedTitle = "Welcome: Mercury Tours";
          String actualTitle = driver.getTitle();
          Assert.assertEquals(actualTitle, expectedTitle);
     }
      @AfterTest
      public void terminateBrowser(){
          driver.close();
      }
}

Applying the logic presented by the table and the code above, we can predict that the sequence by which methods will be executed is:

• 1st - launchBrowser()
• 2nd - verifyHomepageTitle()
• 3rd - terminateBrowser()

The placement of the annotation blocks can be interchanged without affecting the chronological order by which they will be executed. For example, try to rearrange the annotation blocks such that your code would look similar to the one below.

package firsttestngpackage;
import org.openqa.selenium.*;
import org.openqa.selenium.firefox.FirefoxDriver;
import org.testng.Assert;
import org.testng.annotations.*;
public class firsttestngfile {
    public String baseUrl = "http://demo.guru99.com/test/newtours/";
    String driverPath = "C:\\geckodriver.exe";
    public WebDriver driver ; 
     @AfterTest                            //Jumbled
      public void terminateBrowser(){
          driver.close();
      }
     @BeforeTest                            //Jumbled
      public void launchBrowser() {
          System.out.println("launching firefox browser"); 
          System.setProperty("webdriver.firefox.marionette", driverPath);
          driver = new FirefoxDriver();
          driver.get(baseUrl);
      }
      @Test                                //Jumbled
      public void verifyHomepageTitle() {
          String expectedTitle = "Welcome: Mercury Tours";
          String actualTitle = driver.getTitle();
          Assert.assertEquals(actualTitle, expectedTitle);
     }
      
}

Run the code above and notice that

@BeforeMethod and @AfterMethod

In Mercury Tours, suppose we like to verify the titles of the target pages of the two links below.

The flow of our test would be:

• Go to the homepage and verify its title.
• Click REGISTER and verify the title of its target page.
• Go back to the homepage and verify if it still has the correct title.
• Click SUPPORT and verify the title of its target page.
• Go back to the homepage and verify if it still has the correct title.

The code below illustrates how @BeforeMethod and @AfterMethod are used to efficiently execute the scenario mentioned above.

package firsttestngpackage;
import org.openqa.selenium.*;
import org.openqa.selenium.firefox.FirefoxDriver;
import org.testng.Assert;
import org.testng.annotations.*;
@Test
public class firsttestngfile {
    public String baseUrl = "http://demo.guru99.com/test/newtours/";
    String driverPath = "C:\\geckodriver.exe";
    public WebDriver driver; 
    public String expected = null;
    public String actual = null;
        @BeforeTest
      public void launchBrowser() {
          System.out.println("launching firefox browser"); 
          System.setProperty("webdriver.firefox.marionette", driverPath);
          driver= new FirefoxDriver();
          driver.get(baseUrl);
      }
      
      @BeforeMethod
      public void verifyHomepageTitle() {
          String expectedTitle = "Welcome: Mercury Tours";
          String actualTitle = driver.getTitle();
          Assert.assertEquals(actualTitle, expectedTitle);
      }
          @Test(priority = 0)
      public void register(){
          driver.findElement(By.linkText("REGISTER")).click() ;
          expected = "Register: Mercury Tours";
          actual = driver.getTitle();
          Assert.assertEquals(actual, expected);
      }
          @Test(priority = 1)
      public void support() {
            driver.findElement(By.linkText("SUPPORT")).click() ;
            expected = "Under Construction: Mercury Tours";
            actual = driver.getTitle();
            Assert.assertEquals(actual, expected);
      }
      @AfterMethod
      public void goBackToHomepage ( ) {
            driver.findElement(By.linkText("Home")).click() ;
      }
       
      @AfterTest
      public void terminateBrowser(){
          driver.close();
      }
}

After executing this test, your TestNG should report the following sequence.

Simply put, @BeforeMethod should contain methods that you need to run before each test case while @AfterMethod should contain methods that you need to run after each test case.

Summary of TestNG Annotations

@BeforeSuite: The annotated method will be run before all tests in this suite have run.

@AfterSuite: The annotated method will be run after all tests in this suite have run.

@BeforeTest: The annotated method will be run before any test method belonging to the classes inside the tag is run.

@AfterTest: The annotated method will be run after all the test methods belonging to the classes inside the tag have run.

@BeforeGroups: The list of groups that this configuration method will run before. This method is guaranteed to run shortly before the first test method that belongs to any of these groups is invoked.

@AfterGroups: The list of groups that this configuration method will run after. This method is guaranteed to run shortly after the last test method that belongs to any of these groups is invoked.

@BeforeClass: The annotated method will be run before the first test method in the current class is invoked.

@AfterClass: The annotated method will be run after all the test methods in the current class have been run.

@BeforeMethod: The annotated method will be run before each test method.

@AfterMethod: The annotated method will be run after each test method.

@Test: The annotated method is a part of a test case

Conclusion

• TestNG is a testing framework that is capable of making Selenium tests easier to understand and of generating reports that are easy to understand.
• The main advantages of TestNG over JUnit are the following.
  • Annotations are easier to use and understand.
  • Test cases can be grouped more easily.
  • TestNG allows us to create parallel tests.
• The Console window in Eclipse generates a text-based result while the TestNG window is more useful because it gives us a graphical output of the test result plus other meaningful details such as:
  • Runtimes of each method.
  • The chronological order by which methods were executed
• TestNG is capable of generating HTML-based reports.
• Annotations can use parameters just like the usual Java methods.

TestNG is a Testing framework that covers different types of test designs like unit, functional, end to end, UI and integration test.

You can run a single or multiple packages (package here means to encapsulate a group of classes in a proper director format) by creating XML and run it through maven.

In this tutorial, you will learn-

• TestNG Groups with Example
• Set maven and Java path in environment variable (for windows user)
• Introduction to XML and how to make an XML files
• Another mechanism instead of Grouping is “exclude” or “include” in test XML
• How to run code using XML file (video demo)

TestNG Groups with Example

We use groups in Testng when,

• We don't want to define test methods separately in different classes (depending upon functionality) and
• At the same time want to ignore (not to execute) some test cases as if they does not exist in the code.
• So to carry out this we have to Group them. This is done by using "include" and "exclude" mechanism supported in testNG.

In below example, we have shown the syntax of how to use groups in the XML file.

@Test (groups = { "bonding", "strong_ties" })	

Here we are using 2 group names i.e. "bonding" and "strong_ties" (these are logical name that can be altered as per your wish).

<groups> tag defines the starting of groups in XML.

Customize your XML to pick the mentioned group from the test classes. Below mentioned is the syntax of how to declare groups in XML file e.g.

 <groups>		
   <run>		
    <include name="bonding" />		
   </run>		
  </groups>		

So, let us assume that there are 10 test methods in a class.

Out of them,

• 6 methods are tagged in "bonding" group and
• 4 are in "strong_ties" group

Moving forward, we are going to set maven/Java path and use the Eclipse IDE to demonstrate the usage of groups using XML files in Java based maven project.

Set maven and Java path in environment variable (for windows user)

Please refer https://www.guru99.com/maven-jenkins-with-selenium-complete-tutorial.html

https://www.guru99.com/install-java.html

Introduction to XML and how to make an XML files

• XML (Extensible Markup Language) file in Maven framework contains the information of one or more tests and is defined by the tag <suite>.
• Test information in XML is represented by tag <test> and can contain one or more TestNG classes.
• A Java class which contains @Test annotation above test methods is defined as TestNG methods.

Multiple tags are used in a sequence to build a working testNG xml like <suite>, <test> and <class>

• First is <suite> tag, which holds a logical name which defines full information to testNG reported to generate execution report.
• Second is <test name="Guru 99 Smoke Test Demo">, note it is logical name which holds the information of test execution report like pass, fail, skip test cases and other information like total time for execution and group info
• Third is <class name="com.group.guru99.TC_Class1" />, com.group.guru99 is the package used, and Test Class name is TC_Class1.

<?xml version="1.0" encoding="UTF-8" ?>	
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">	
 	<suite name="Suite">	
		<test name="Guru 99 Smoke Test Demo">	
			<groups>	
				<run>	
   					 <include name="strong_ties" />	
        		</run>	
       		</groups>	
			<classes>	
					<class name="com.group.guru99.TC_Class1" />	
           	</classes>	
		</test>	
  </suite>	

We will be using this XML for upcoming video downside.

Another mechanism instead of Grouping is "exclude" or "include" in test XML

Suppose you are finding the usage of group mechanism complex then testNG XML facilitate the functionality to exclude/include a test.

Exclude Tag:  Syntax for exclude tag <exclude name="${TEST_CASE_NAME}" />
Include Tag:  Syntax for include tag <include name="${TEST_CASE_NAME}" />

Note: We can include/exclude multiple test cases once at a time, and it works with Groups as well.

How to run code using XML file (video demo)

Explanation of the Java Code and XML with the group, exclude and include the tag in XML.

• Scenario: Launch Guru99 demo Banking site, verify few thing's on login page after that enter credentials and re-verify few new thing on the application when logged in.

  

Note: Each step which you code should be declared in separate methods, but when executed, it will execute test methods depending upon the entries in the XML file.

Method 1: Initialize Browser and launch URL (tc01LaunchURL())

Method 2: Verify Login Page Heading (tc02VerifyLaunchPage())

Method 3: Enter userName and Password on login form (tc03EnterCredentials())

Method 4: Verify the presence of Manager ID on User Dashboard (tc04VerifyLoggedInPage())

Method 5: Verify few more links on User DashBoard (tc05VerifyHyperlinks())

Code for our scenario:

package com.group.guru99;	

import java.util.concurrent.TimeUnit;	

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

public class TC_Class1 {	
    public static final WebDriver webDriver = new FirefoxDriver();;	

    String launchPageHeading = "//h3[text()='Guru99 Bank']";	
    final String userName_element = "//input[@name='uid']", password_element = "//input[@name='password']",	
            signIn_element = "//input[@name='btnLogin']";	
    final String userName_value = "mngr28642", password_value = "ydAnate";	
    final String managerID = "//td[contains(text(),'Manger Id')]";	
    final String newCustomer = "//a[@href='addcustomerpage.php']", fundTransfer = "//a[@href='FundTransInput.php']";	

    /**	
     * This test case will initialize the webDriver	
     */	
    @Test(groups = { "bonding", "strong_ties" })	
    public void tc01LaunchURL() {	
        webDriver.manage().window().maximize();	
        webDriver.manage().timeouts().implicitlyWait(20, TimeUnit.SECONDS);	
        webDriver.get("http://www.demo.guru99.com/V4/");	
    }	

    /**	
     * Will check the presence of Heading on Login Page	
     */	
    @Test(groups = { "bonding" })	
    public void tc02VerifyLaunchPage() {	
        Assert.assertTrue(webDriver.findElement(By.xpath(launchPageHeading)).isDisplayed(),	
                "Home Page heading is not displayed");	
        System.out.println("Home Page heading is displayed");	
    }	

    /**	
     * This test case will enter User name, password and will then click on	
     * signIn button	
     */	
    @Test(groups = { "bonding", "strong_ties" })	
    public void tc03EnterCredentials() {	
        webDriver.findElement(By.xpath(userName_element)).sendKeys(userName_value);	
        webDriver.findElement(By.xpath(password_element)).sendKeys(password_value);	
        webDriver.findElement(By.xpath(signIn_element)).click();	
    }	

    /**	
     * This test case will verify manger's ID presence on DashBoard	
     */	
    @Test(groups = { "strong_ties" })	
    public void tc04VerifyLoggedInPage() {	
        Assert.assertTrue(webDriver.findElement(By.xpath(managerID)).isDisplayed(),	
                "Manager ID label is not displayed");	
        System.out.println("Manger Id label is displayed");	
    }	

    /**	
     * This test case will check the presence of presence of New customer link	
     * And FundTransfer link in Left pannel	
     */	
    @Test(groups = { "bonding" })	
    public void tc05VerifyHyperlinks() {	
        Assert.assertTrue(webDriver.findElement(By.xpath(newCustomer)).isEnabled(),	
                "New customer hyperlink is not displayed");	
        System.out.println("New customer hyperlink is displayed");	

        Assert.assertTrue(webDriver.findElement(By.xpath(fundTransfer)).isEnabled(),	
                "Fund Transfer hyperlink is not displayed");	
        System.out.println("Fund Transfer hyperlink is displayed");	
    }	

}	

Please Note: The credentials are only valid for 20 days, so if you are trying to run code on your local machine, so you might face invalid credentials error. Please find below steps to generate your login credentials:

1. Launch http://www.demo.guru99.com
2. Enter your email id in the box.
3. Click enter and see your login details on screen.

Explanation of Code:

As mentioned above, we have created 5 test cases for performing each action in independent methods.

You can observe that to every method, we have associated a group parameter holding some value in it.

Basically, these are the name of the differentiating groups i.e. "strong_ties" & "bonding".

• First and Third methods are tagged to "bonding", "strong_ties" which means if XML is updated in any of the group, this Test Case will run.
• The second method is only tagged to "bonding" group it means that if XML is updated with bonding group. Only in that case this test case will run.
• Fourth Test case is tagged to strong_ties group, which means this test case will only run if XML is updated with strong_ties group name.
• Last but not the least fifth test case is attached to bonding group, which means this test case will only run if XML is updated with bonding group name.

So overall, we have 4 scenarios;

1. We want to run all test cases irrespective of the group name. In this case, we will remove Group tag from running XML.

1. We want to run test case few test that are related only to either of groups i.e. strong_ties or bonding

• Please refer:

   

• In this video, Group parameter is commented from running XML. Hence, you will see all test cases were executed.

• In continuation to video, now we have included group name in XML, you can see only test cases specific to that group is only running.

1. We are using Exclude mechanism to exclude the test case:

• Please refer

   

• You see that we have used exclude few test case (tc02) by writing their name in running XML. In final result mentioned test cases did not run.

1. Last, we are using include test mechanism to include the test cases (tc01LaunchURL, tc03EnterCredentials and tc05VerifyHyperlinks)
   • Please refer

      

   • In this video, you will see that test cases which are mentioned in XML are only running during the test execution.

Please download code from the mentioned URL, it will contain all type of testXML:

Download the above Code

Conclusion

We have learned here relatively a new way for running test cases using XML in Maven project.

We started by providing a brief introduction on testNG and continued with the full technical specification of Groups, exclude and include.

 

TestNG is a Testing framework, that covers different types of test designs like a unit test, functional test, end to end test, UI test and integration test.

You can run a single or multiple test cases in your Testng code.

If test priority is not defined while, running multiple test cases, TestNG assigns all @Test a priority as zero(0).

Now, while running; lower priorities will be scheduled first.

In this tutorial, you will learn -

• Demo of TestNG code without Priority
• Demo of TestNG code without Priority in Alphabetical Order
• How to set Priority in TestNG
• Methods with Same Priority
• Combining both prioritized(having same priority) and non-prioritized methods

Demo of TestNG code without Priority

Let's take a scenario where sequencing will be required in order to pass all test cases:

Scenario: Generate a code where you are required to perform a Google search with a specific keyword say "Facebook". Now, verify that Browser title is changed to "Facebook - Google Search".

Note: Each step which you code should be in separate methods

Method 1: Open Browser say Firefox (openBrowser())

Method 2: Launch Google.com (launchGoogle())

Method 3: Perform a search using "Facebook" (performSearchAndClick1stLink())

Method 4: Verify Google search page title (FaceBookPageTitleVerification())

Code for our scenario:

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

public class Priority_In_testNG {		
    WebDriver driver;			

	    // Method 1: Open Brower say Firefox			
	    @Test		
	    public void openBrowser() {				
	        driver = new FirefoxDriver();				
	    }		

	    // Method 2: Launch Google.com			
	    @Test		
	    public void launchGoogle() {				
	        driver.get("http://www.google.co.in");						
	    }		
        
	    // Method 3: Perform a search using "Facebook"			
	    @Test		
	    public void peformSeachAndClick1stLink() {				
	        driver.findElement(By.xpath(".//*[@title='Search']")).sendKeys("Facebook");								
	    }		

	    // Method 4: Verify Google search page title.			
	    @Test		
	    public void FaceBookPageTitleVerification() throws Exception {				
	        driver.findElement(By.xpath(".//*[@value='Search']")).click();						
	        Thread.sleep(3000);		
	        Assert.assertEquals(driver.getTitle().contains("Facebook - Google Search"), true);				
	    }		
	}		

Explanation of Code

As mentioned above we have created 4 test cases for performing each action in an independent methods.

• The first method (openBrowser) states to initialize Firefox browser.
• The second method (launchGoogle) states that launch Google.com is in the initialized browser.
• The third method (peformSeachAndClick1stLink)states that perform a search in the search box (with xpath (".//*[@title='Search']") with a search term as Facebook and
• The fourth and last method (FaceBookPageTitleVerification) states that click on search icon of Google and verify that browser title has been changed to Facebook - Google Search.

Now run this code using testNG as shown in the video you will find all the Test Case are failing. The reason for failure: as there is a dependency of previous test case to pass, only than current running test case will be passed.

In this case,

• First method which is executed is openBrowser(). It got passed because it does not have any dependency.
• Second method executed is FaceBookPageTitleVerification(); it is failing because we are trying to click search button and verifying browser title.
• You can see that if search activity is not process then how any other step can get passed. Hence, this is the reason my test cases are failing.

PASSED: openBrowser
FAILED: FaceBookPageTitleVerification
FAILED: launchGoogle
FAILED: peformSeachAndClick1stLink

Demo of TestNG code without Priority in Alphabetical Order

If we don’t mention any priority, testng will execute the @Test methods based on alphabetical order of their method names irrespective of their place of implementation in the code.

package com.guru.testngannotations;

import org.testng.annotations.Test;

public class TestNG_Priority_Annotations {

@Test
public void c_method(){
System.out.println("I'm in method C");
}
@Test
public void b_method(){
System.out.println("I'm in method B");
}
@Test
public void a_method(){
System.out.println("I'm in method A");
}
@Test
public void e_method(){
System.out.println("I'm in method E");
}
@Test
public void d_method(){
System.out.println("I'm in method D");
}

}

Output

I'm in method A 
I'm in method B 
I'm in method C 
I'm in method D 
I'm in method E 

Though we defined the methods in a random manner (c, b, a, e, d), testng executed the methods based on their method names by considering alphabetical order and the same was reflected in the output as well.

How to set Priority in TestNG

As you have seen in the previous example that sequencing required in order to pass this scenario, so we will be modifying the previous piece of code with Priority Parameter so that each test should run against to the priority assigned to them.

Now as you can see we have assigned the Priority to each test case means test case will the lower priority value will be executed first.

Priority in testNG in action

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

public class Priority_In_testNG {		
    WebDriver driver;			

    // Method 1: Open Browser say Firefox			
    @Test (priority=1)		
    public void openBrowser() {				
        driver = new FirefoxDriver();				
    }		

    // Method 2: Launch Google.com			
    @Test (priority=2)		
    public void launchGoogle() {				
        driver.get("http://www.google.co.in");						
    }		

    // Method 3: Perform a search using "Facebook"			
    @Test (priority=3)		
    public void peformSeachAndClick1stLink() {				
        driver.findElement(By.xpath(".//*[@title='Search']")).sendKeys("Facebook");								
    }		

    // Method 4: Verify Google search page title.			
    @Test (priority=4)		
    public void FaceBookPageTitleVerification() throws Exception {				
        driver.findElement(By.xpath(".//*[@value='Search']")).click();						
        Thread.sleep(3000);		
        Assert.assertEquals(driver.getTitle().contains("Facebook - Google Search"), true);				
    }		
}		

Explanation of Code

After assigning priority to each testcases, run the above code using testNG as shown in Video-2 mentioned below.

Here, you can see that test cases are prioritized. Test case having lower priority are executed first i.e. now there is a sequential execution according to priority in the test cases. Hence, all test cases are passing now.

Note the console of eclipse:

Output :

PASSED: openBrowser
PASSED: launchGoogle
PASSED: peformSearchAndClick1stLink
PASSED: FaceBookPageTitleVerification

Number 0 has the highest priority(it’ll be executed first) and the priority goes on based on the given number i.e., 0 has the highest priority than 1. 1 has the highest priority than 2 and so on.

package com.guru.testngannotations;
import org.testng.annotations.Test;

public class TestNG_Priority_Annotations {

    @Test(priority=6)
    public void c_method(){
    System.out.println("I'm in method C");
    }
    @Test(priority=9)
    public void b_method(){
    System.out.println("I'm in method B");
    }
    @Test(priority=1)
    public void a_method(){
    System.out.println("I'm in method A");
    }
    @Test(priority=0)
    public void e_method(){
    System.out.println("I'm in method E");
    }
    @Test(priority=3)
    public void d_method(){
    System.out.println("I'm in method D");
    }

}

Output

I'm in method E 
I'm in method A 
I'm in method D 
I'm in method C 
I'm in method B 

Here we have provided the priorities as 0,1,3,6,9. So, method having 0 as priority is executed first and then method having priority-1 and so on. Here alphabetical order method name won’t be considered as we provided the priorities

Methods with Same Priority:

There may be a chance that methods may contain same priority. In those cases, testng considers the alphabetical order of the method names whose priority is same.

package com.guru.testngannotations;
import org.testng.annotations.Test;

public class TestNG_Priority_Annotations {

    @Test(priority=6)
    public void c_method(){
    System.out.println("I'm in method C");
    }
    @Test(priority=9)
    public void b_method(){
    System.out.println("I'm in method B");
    }
    @Test(priority=6)
    public void a_method(){
    System.out.println("I'm in method A");
    }
    @Test(priority=0)
    public void e_method(){
    System.out.println("I'm in method E");
    }
    @Test(priority=3)
    public void d_method(){
    System.out.println("I'm in method D");
    }

}

Output

I'm in method E 
I'm in method D 
I'm in method A 
I'm in method C 
I'm in method B 

Here ‘e’ and ‘d’ are executed based on their priority values. But the methods ‘a’ and ‘c’ contains the same priority value(6). So, here testng considers the alphabetical order of ‘a’ and ’c’ and executes them accordingly.

Combining both prioritized(having same priority) and non-prioritized methods:

In this case, we’ll cover two cases in one testng class.

1. Methods having same priority value.
2. More than one non-prioritized methods.

package com.guru.testngannotations;

import org.testng.annotations.Test;

public class TestNG_Priority_Annotations {

	@Test()
	public void c_method(){
		System.out.println("I'm in method C");
	}
	@Test()
	public void b_method(){
		System.out.println("I'm in method B");
	}
	@Test(priority=6)
	public void a_method(){
		System.out.println("I'm in method A");
	}
	@Test(priority=0)
	public void e_method(){
		System.out.println("I'm in method E");
	}
	@Test(priority=6)
	public void d_method(){
		System.out.println("I'm in method D");
	}
}

Output:

I'm in method B 
I'm in method C 
I'm in method E 
I'm in method A 
I'm in method D 

PASSED: b_method 
PASSED: c_method 
PASSED: e_method 
PASSED: a_method 
PASSED: d_method

Explanation:

First preference: Non-prioritized methods: ‘c’ and ‘b’: Based on alphabetical order ‘b’ was executed first and then ‘c’.

Second preference: Prioritized methods: ‘a’, ‘e’ and ‘d’: ‘e’ was executed first as it was having highest priority(0). As the priority of ‘a’ and ‘d’ methods were same, testng considered the alphabetical order of their methods names. So, between them, ‘a’ was executed first and then ‘d’.

Case-sensitive in TestNG

Just for your information there is a standard syntax for defining priority in testNG i.e. @Test (priority=4), suppose you are defining it in some other syntax say @Test (PRIORITY=1) then your IDE will show it as a compilation error. Refer image below:

Conclusion:

As you have seen that if there is a requirement to run a set of test-case in specific sequence then it can be easily done using Priority using testNG as a run tool.

This tutorial is made possible due to contributions of Ramandeep Singh and Rama Krishna Gadde

import org.openqa.selenium.WebDriver;
import org.openqa.selenium.firefox.FirefoxDriver;
public class SessionHandling {
public static void main(String...strings ){
    //First session of WebDriver
    WebDriver driver = new FirefoxDriver();
    //Goto guru99 site
    driver.get("http://demo.guru99.com/V4/");
    
    //Second session of WebDriver
    WebDriver driver2 = new FirefoxDriver();
    //Goto guru99 site
    driver2.get("http://demo.guru99.com/V4/");
}
}

import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
import org.testng.annotations.Test;
public class TestGuru99MultipleSession {
    @Test    
    public void executSessionOne(){
            //First session of WebDriver
        System.setProperty("webdriver.chrome.driver","chromedriver.exe");
            WebDriver driver = new ChromeDriver();
            //Goto guru99 site
            driver.get("http://demo.guru99.com/V4/");
            //find user name text box and fill it
            driver.findElement(By.name("uid")).sendKeys("Driver 1");
            
        }
        
    @Test    
        public void executeSessionTwo(){
            //Second session of WebDriver
        System.setProperty("webdriver.chrome.driver","chromedriver.exe");
        WebDriver driver = new ChromeDriver();
            //Goto guru99 site
        driver.get("http://demo.guru99.com/V4/");
        //find user name text box and fill it
        driver.findElement(By.name("uid")).sendKeys("Driver 2");
        
        }
        
    @Test    
        public void executSessionThree(){
            //Third session of WebDriver
        System.setProperty("webdriver.chrome.driver","chromedriver.exe");
        WebDriver driver = new ChromeDriver();
            //Goto guru99 site
        driver.get("http://demo.guru99.com/V4/");
        //find user name text box and fill it
        driver.findElement(By.name("uid")).sendKeys("Driver 3");
        
        }        
}

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name="TestSuite" thread-count="3" parallel="methods" >
<test name="testGuru">
<classes>
<class name="TestGuru99MultipleSession">
</class>
</classes>
</test>
</suite>

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name="TestSuite" thread-count="3" parallel="methods" >
<test name="testGuru">
<classes>
<class name="TestGuru99MultipleSession">
<include value="testGuru99TC1" dependsOnMethods=" testGuru99TC2"/>
<include value="testGuru99TC2"/>
</class>
</classes>
</test>
</suite>

package Listener_Demo;		

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

public class ListenerTest implements ITestListener						
{		

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

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

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

    @Override		
    public void onTestFailure(ITestResult arg0) {					
        // TODO Auto-generated method stub				
        		
    }		

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

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

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

onTestFailure, onTestSkipped, onTestStart, onTestSuccess, etc.

package Listener_Demo;		

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

public class ListenerTest implements ITestListener						
{		

    @Override		
    public void onFinish(ITestContext Result) 					
    {		
                		
    }		

    @Override		
    public void onStart(ITestContext Result)					
    {		
            		
    }		

    @Override		
    public void onTestFailedButWithinSuccessPercentage(ITestResult Result)					
    {		
    		
    }		

    // When Test case get failed, this method is called.		
    @Override		
    public void onTestFailure(ITestResult Result) 					
    {		
    System.out.println("The name of the testcase failed is :"+Result.getName());					
    }		

    // When Test case get Skipped, this method is called.		
    @Override		
    public void onTestSkipped(ITestResult Result)					
    {		
    System.out.println("The name of the testcase Skipped is :"+Result.getName());					
    }		

    // When Test case get Started, this method is called.		
    @Override		
    public void onTestStart(ITestResult Result)					
    {		
    System.out.println(Result.getName()+" test case started");					
    }		

    // When Test case get passed, this method is called.		
    @Override		
    public void onTestSuccess(ITestResult Result)					
    {		
    System.out.println("The name of the testcase passed is :"+Result.getName());					
    }		

}			

package Listener_Demo;		

import org.openqa.selenium.By;		
import org.openqa.selenium.WebDriver;		
import org.openqa.selenium.firefox.FirefoxDriver;		
import org.testng.Assert;		
import org.testng.annotations.Listeners;		
Import org.testng.annotations.Test;		

public class TestCases {				
WebDriver driver= new FirefoxDriver();					

// Test to pass as to verify listeners .		
@Test		
public void Login()				
{		
    driver.get("http://demo.guru99.com/V4/");					
    driver.findElement(By.name("uid")).sendKeys("mngr34926");							
    driver.findElement(By.name("password")).sendKeys("amUpenu");							
    driver.findElement(By.name("btnLogin")).click();					
}		

// Forcefully failed this test as to verify listener.		
@Test		
public void TestToFail()				
{		
    System.out.println("This method to test fail");					
    Assert.assertTrue(false);			
}		
}

@Listeners(Listener_Demo.ListenerTest.class)				

package Listener_Demo;		

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

@Listeners(Listener_Demo.ListenerTest.class)			

public class TestCases {				
WebDriver driver= new FirefoxDriver();					

//Test to pass as to verify listeners.		
@Test		
public void Login()				
{		
    driver.get("http://demo.guru99.com/V4/");					
    driver.findElement(By.name("uid")).sendKeys("mngr34926");							
    driver.findElement(By.name("password")).sendKeys("amUpenu");							
    driver.findElement(By.id("")).click();					
}		

//Forcefully failed this test as verify listener.		
@Test		
public void TestToFail()				
{		
    System.out.println("This method to test fail");					
    Assert.assertTrue(false);			
}		
}			

[TestNG] Running:		
C:\Users\gauravn\AppData\Local\Temp\testng-eclipse--1058076918\testng-customsuite.xml		

Login Test Case started		
The name of the testcase passed is:Login		
TestToFail test case started		
This method to test fail		
The name of the testcase failed is:TestToFail		
PASSED: Login		
FAILED: TestToFail		
java.lang.AssertionError: expected [true] but found [false]			

In this tutorial, you will learn-

• Create a Selenium Project
• Convert and Execute Selenium Project to TestNG
• Execute TestNG via Command Line
• How to run only failed test cases
• Running testng-failed.xml file from Command line

Create a Selenium Project

Prepare the Project

Step 1) In Eclipse, Create Java project by clicking on new Java Project

Step 2) In this step,

1. Give project Name
2. Choose execution environment
3. Select Project layout option
4. Click on "Finish" button.

When you click on finish button. The "TestProject" java project is created. The "TestProject" will look like this.

Step 3) Open that newly created project. You will able to see the "src" folder in Package Explorer.

1. Right click project and select "New"
2. Select option package

Step 4) In this step,

1. Browse the src folder and select package
2. Give the package name and
3. Finally, click on finish button. (package Name->com.test)

After clicking on "finish" the project structure will look like this:

Step 5) In this step,

1. Now, Right click on newly created package and
2. Select option "class."

A new window will open.

Step 6) In this step,

1. Give the "class" name
2. Select modifiers
3. Browse and select superclass java.lang.object
4. Click on finish button.

Here, you are creating two classes ex: DemoA, DemoB.

First Create Class DemoA.

When you click on "Finish" Button. Then it will going to create class like this:

Similarly, create class DemoB, When you click on "Finish" Button class will look like below-

Step 7) If you have installed TestNG library just click on Java Project--->Properties.

Step 8) Now in properties window,

1. Click on Java Build Path
2. Click on Libraries
3. Click on Add Library.

Next

1. Click on "TestNg" and then
2. Click on "Next".

Then Click on "finish" button.

After this, write the following code.

For Class DemoA

Code Explanation:

• Driver.manage().window().maximize();

This line will going to maximize the Browser window.

• driver.get(https://www.google.co.in);

This line will enter the specified URL in the URL field.

• driver.findElement(By.name("q")).sendKeys("Hi");

This line will going to identify the "Google" search box and enter the data you sent using sendKeys method.

Output: The above program contains the errors, so it is not possible to execute.

Similarly for Class DemoB,

The red color underlined words are the errors here. Because you have not yet added the jar file that contains these classes and interfaces. In order to remove the errors present in the above code add the corresponding jar file. Right click on the Java Project and Select "Properties".

Step 8) In the property window,

1. Click on Java Build path on the left navigation pane.
2. Click on the libraries tab,
3. Click on the Add External JARs and Select the Selenium-standalone jar file
4. Click on "OK" button.

After this step, all the errors will be removed automatically. If not then place the mouse over the code which is showing errors and import all necessary classes and interfaces.

For @test if it is still showing errors then place the mouse over there. It will show the possible options. Then click on add TestNG Library option. Similarly do it for other 'class' also.

After writing your code inside both the classes i.e. DemoA, DemoB go to the next step.

Step 9) In this step,

1. Right-click on the Project and
2. Select option folder to create a folder called 'lib' and paste testNG jar file and selenium jar file (selenium-server-standalone<version>).

   (Testng and Selenium-server-standalone jar file need to be downloaded from web and store it inside your system. You need to manually go to that folder and copy these two jars and right click on 'lib' folder present in eclipse and click on paste)

Step 10) In this step,

1. Select the parent folder

2. Give the Folder name as 'lib' and (The primary purpose of adding these two jar files in the lib folder is that, while executing from the command prompt you can tell the compiler that the required jar files for the execution of the program are present in this location. If you want to execute testng.xml from eclipse then this lib folder is not at all required)

3. Click on 'finish' button

Testng and Selenium-server-standalone jar file need to be downloaded from web and store it inside your system. You need to manually go to that folder and copy these two jars and right click on 'lib' folder present in eclipse and click on paste

After creating a folder, next step will be converting our programs that are DemoA and DemoB into Testng.xml file.

Convert and Execute Selenium Project to TestNG

Step 1) In this step,

1. Select two java files present under the package and right click.
2. Select the option called "testNG."
3. Click on convert to "testNG".

Step 2) A new window will open. In this window, enter details like

1. Location
2. Suite Name
3. Test Name
4. Class Selection
5. Parallel Mode
6. Click on "Finish" button

Then the testng.xml file created under the java project, and it will look like this.

(if you want to run that testng.xml file then Right click on that testng.xml file present on the left navigation pane in Package Explorer and click on run as TestNG Suite. )

Step 3) The testng.xml suite file will look like this:

If you want to execute DemoA class first, then remove that complete line and add it before DemoB class like this:

Step 4) After executing the testng.xml file, it will display the result in the following manner. (Since you have not written any executable statements using System.out.println() so it is not printing anything on the console window).

This is one of the ways you will execute test through the eclipse, if you want to execute the same testng.xml suite file that contains two class file such as DemoA, DemoB from the command prompt you need to follow the below steps.

Now open the command prompt and go to the Project workspace.

Execute TestNG via Command Line

You need to find the location of the Project Space

Step 1) First right click on the Java Project and Select the properties option. In properties window select option resource.

Step 2) Now when you click on "resource" link, present in the left navigation pane. It will show where exactly the project is stored

The project workspace is C:\Users\User\Desktop\Guru99\TestProject. So you are changing directory to that particular location.

Step 3) Then type the following command. (This command is generic command)

java –cp "path of lib folder present in workspace\*; path of bin folder present in project workspace; path of testng.jar file present in lib folder of project workspace" org.testng.TestNG testng.xml

but for our project you need to write the following command.

Java –cp  "C:\Users\User\Desktop\Guru99\TestProject\lib\*;
  C:\Users\User\Desktop\Guru99\TestProject\bin" org.testng.TestNG testng.xml

Step 4) Then press the Enter. Both the classes DemoA and DemoB will start their execution. Finally, it will display the result on the command prompt.

How to run only failed test cases

If you want to execute only failed test cases through the Eclipse, then first refresh the project.

Step 1) Right click on the java project (Demo A and B). Select the refresh option or simply select the java project and press F5.

Step 2) Then you will able to see the test-output folder. In that folder, you have a file with name testng-failed.xml.

Step 3) Right-click on this file and click on run as and select the option called "testNG suite".

Suppose if you have three test cases if all the test cases are executed successfully means you are not able to see this folder under the test-output folder. This folder will appear only when one of the test case is failed. Then run this file, it will going to run only failed test cases.

Running testng-failed.xml file from Command line

Step 1) To run failed test cases in command prompt. Open the command prompt and go to the Project workspace.

My project workspace is C:\Users\User\Desktop\Guru99\TestProject. So you will be changing directory to that particular location.

Step 2) Type the following command. (This command is generic command)

java –cp "path of lib folder present in workspace\*; path of bin folder present in project workspace; path of testing.jar file present in lib folder of project workspace" org.testng.TestNG test-output/testng-failed.xml

For our project, you need to write the following command.

Java –cp "C:\Users\User\Desktop\Guru99\TestProject\lib\*;
C:\Users\User\Desktop\Guru99\TestProject\bin" org.testng.TestNG test-output/testng-failed.xml

Step 3) Then press the Enter. It will going to run only failed classes and display corresponds to that class only.

In the above class i.e. DemoB just change the code like this.

driver.findElement(By.name("a")).sendKeys("Bye");		

The above code will not going to find any element. So, it will throw the exception. But in our program, you are not handling the exception so our program will stop executing the remaining code. Because of this reason, the ClassB will going to fail.

Summary:

• TestNG is Automation Testing Framework which is inspired from the Junit and contains different annotations.
• TestNG generates the reports in its standard report,which contains the following things:
  • How many test cases are there ?
  • How many test cases are passed ?
  • How many test cases are failed ?
  • How many test cases are skipped ?
• Multiple test cases can be grouped easily and executed them by converting test classes into testing suite file.
• TestNG can be easily integrated with other third-party tools. It provides different features like assigning the priority to the test cases, execution of same test case multiple times using invocation count.
• If any of the test case fails while executing multiple test cases, you can execute that specific test case separately.
• The static method "log" of Reporter class can be used to store logging information which is present in org.testng

This article is contributed by Sandeep Batageri

Report generation is very important when you are doing the Automation Testing as well as for Manual Testing.

• By looking at the result, you can easily identify how many test cases are passed, failed and skipped.
• By looking at the report, you will come to know what the status of the project is.

Selenium web driver is used for automating the web-application, but it won't generate any reports.

• The TestNG will generate the default report.
• When you execute testng.xml file, and refresh the project. You will get test-output folder in that folder.
• Right click on the emailable-report.html and select the option. Open with the web browser.

In this tutorial, you will learn-

• Method-1: emailable-report.html
• Method-2: index.html
• Method-3: Reporter Class

Method-1: emailable-report.html

1. Click on option "emailable-report.html"
2. Click on option web browser

The output report of testng will look like below if both the classes are passed:

Consider the scenario in where you are intentionally failing the test case i.e. DemoB class. Then convert both the classes into testng.xml suite file and run it. Then the result will look like this. It will show the failed test cases.

This is result for DemoB class:

Similarly, result for the Class DemoA will look like this:

Method-2 index.html

1. Right click on the index.html from the project directory.
2. Select option open with web browser option. It will display the result in the following order.

The result will look like this:

Method-3 Reporter Class

Along with these report generated methods, you can use object.properties file to store the system generated logs as well as user generated logs. But one of the simplest ways to store log information in testing is using Reporter Class.

Reporter is a class present in TestNG. It provides 4 different methods to store log information they are:

1. Reporter.log(String s);
2. Reporter.log(String s, Boolean logToStandardOut);
3. Reporter.log(String s, int level);
4. Reporter.log(String s, int level, Boolean logToStandardOut);

Example:

Create Two classes such as DemoA and DemoB and write the following code inside the classes.

For Class DemoA;

• The Code for DemoA is already explained above. Here you are using log method of Reporter class. (For implementing a reporting class, the class has to implement an org.testng.IReporter interface).
• The log method is a static method of Reporter class. So you are accessing that method through the Reporter class.
• The log method is used to store log information that is written inside the program. By looking at the log information, you will easily come to know where exactly the execution of the program is stopped.

For Class DemoB:

• Now, Create testng.xml file by selecting these two classes and
• Select run as and
• Click on the convert to testng.
• Then run this testng.xml file by selecting run as and select testng suite.
• Then refresh the project open the test-output folder.

1. In the test-output folder, open the emailable-report.html. It will look like:

   

Similarly, you will have an Output for Demo B project as well.

2. In test-output folder open the index.html. It will look like:

Click on reporter output. It will open logging info whatever written in the test methods.

Click on the Times. It will going to show how much time it took to run the test method present in class.