On this page, you can find Selenium Interview questions and answers which may benefit to freshers to experienced professional. This is part 2 of this interview questions series.
1. How to Handle windows authentication popup using any third party tool .
Below are the steps to achieve this Using Autoit (Third Party Tool) –
Download and in Autoit editor write script through below command
ControlFocus(), ControlSet(), ControlClick()
Save file and Compile Script with your version and after that you get .exe file.
Java code for executing .exe file
Runtime.getRuntime().exec(\\Path)
It throws checked exception IOexception.
2. What are the different types of Exceptions in Selenium Webdriver?
5. How to find more than one web element in the list?
At times, we may come across elements of same type like multiple hyperlinks, images etc arranged in an ordered or unordered list. Thus, it makes absolute sense to deal with such elements by a single piece of code and this can be done using WebElement List.
Sample Code:
// Storing the list
List <WebElement> elementList = driver.findElements(By.xpath("//div[@id='example']//ul//li"));
// Fetching the size of the list
int listSize = elementList.size();
for (int i=0; i<listSize; i++)
{
// Clicking on each service provider link
serviceProviderLinks.get(i).click();
// Navigating back to the previous page that stores link to service providers
driver.navigate().back();
}
6. What is the difference between driver.close() and driver.quit command?
close(): WebDriver’s close() method closes the web browser window that the user is currently working on or we can also say the window that is being currently accessed by the WebDriver. The command neither requires any parameter nor does is return any value. quit(): Unlike close() method, quit() method closes down all the windows that the program has opened.
Same as close() method, the command neither requires any parameter nor does is return any value.
7. Difference between findElement/findElements ?
findElement () will return only single WebElement and if that element is not located or we use some wrong selector then it will throw NoSuchElement exception. findElements() will return List of WebElements – for this we need to give locator in such a way that it can find multiple elements and will return you list of webelements then using List we can iterate and perform our operation.
import java.util.List;
import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import org.openqa.selenium.firefox.FirefoxDriver;
public class findElementDemo {
public static void main(String[] args) throws Exception {
WebDriver driver=new FirefoxDriver();
driver.manage().window().maximize();
driver.get("http://google.com");
Thread.sleep(5000);
List<WebElement> links=driver.findElements(By.xpath(".//*[@id='menu-top']/li")); System.out.println("Total element is "+links.size());
Iterator<WebElement> i1=links.iterator();
while(i1.hasNext)
WebElement ele1=i1.next();
String name=ele1.getText();
System.out.println("Elements name is "+name);
}
}
}
8. Difference between assert and verify in selenium Webdriver
When an “assert” fails, the test will be aborted. Assert is best used when the check value has to pass for the test to be able to continue to run log in.
Where if a “verify” fails, the test will continue executing and logging the failure.Verify is best used to check non critical things. Like the presence of a headline element.
9. How will you execute your login script using chrome browser from your editor using selenium?
System.setProperty("webdriver.chrome.driver","C:\\Users\\Public\\Documents\\Selenium\\chromedriver.exe");
WebDriver driver = new ChromeDriver();
10. Can we use multiple catch in try, how ?
Yes, we can use. Refer below Example –
public static void main(String args[]){ try{
int a[]=new int[5];
a[5]=30/0;
}
catch(Exception e)
{
System.out.println("common task completed");
}
catch(ArithmeticException e)
{
System.out.println("task1 is completed");
}
catch(ArrayIndexOutOfBoundsException e)
{
System.out.println("task 2 completed");
}
System.out.println("rest of the code...");
}
}
During automation in Selenium WebDriver, we come across various exceptions & we need to deal with them. Below is the list of various exceptions occur in selenium webdriver.
In general, hierarchy of Exceptions in any language is shown in below image –
There are main three types of Exceptions in Selenium WebDriver –
Checked Exceptions – These Exceptions can be handled during compile time. If they are not handled, it gives compile time error. Example- FileNotFoundException, IOException etc.
Unchecked Exceptions – These exceptions can not be handled during compile time & they got caught at run time. Example – ArrayIndexOutOfBoundException.
Error – Errors which can not be handled by using even try catch block. Example -Assertion Error.
Below are few common exceptions received during selenium scripting in java – selenium.
WebDriverException
WebDriver Exception comes when we try to perform any action on the non-existing driver.
WebDriver driver = new InternetExplorerDriver();
driver.get("http://google.com");
driver.close();
driver.quit();
NoAlertPresentException
When we try to perform an action i.e., either accept() or dismiss() which is not required at a required place; gives us this exception.
When we try to switch to an window which is not present gives us this exception:
WebDriver driver = new InternetExplorerDriver();
driver.get("http://google.com");
driver.switchTo().window("Yup_Fail");
driver.close();
In the above snippet, line 3 throws us an exception, as we are trying to switch to an window that is not present.
NoSuchFrameException
Similar to Window exception, Frame exception mainly comes during switching between the frames.
WebDriver driver = new InternetExplorerDriver();
driver.get("http://google.com");
driver.switchTo().frame("F_fail");
driver.close();
In the above snippet, line 3 throws us an exception, as we are trying to switch to an frame that is not present.
NoSuchElementException
This exception is thrown when we WebDriver doesn’t find the web-element in the DOM.
WebDriver driver = new InternetExplorerDriver();
driver.get("http://google.com");
driver.findElement(By.name("fake")).click();
TimeoutException
Thrown when a command does not complete in enough time.
StaleElementException
StaleElementException occurs if I find an element, the DOM gets updated then I try to interact with the element.
If Javascript updates the page between the findElement call and the click call then I’ll get a StaleElementException. It is not uncommon for this to occur on modern web pages. It will not happen consistently however. The timing has to be just right for this bug to occur.
So how do I handle it? I use the following click method:
public boolean retryingFindClick(By by) { boolean result = false;
int attempts = 0;
while(attempts < 2) {
try {
driver.findElement(by).click();
result = true;
break;
} catch(StaleElementException e) {
}
attempts++;
}
return result;
}
So, these the common exceptions which occur during automation which i tried to cover. Hope this helps !!!!
In this article, i will talk about how to use Map (Hashmap) with TestNG DataProvider for Data Driven Testing in Selenium WebDriver. Before to this, let us understand little more about Map.
What is Map in Java?
—> Map is a interface in java and can implements various classes in java like Hashmap, Hashtable & many other. They are the part of collections framework and are used to handle. store data. Map interface represent the mapping in between key and value. What that mean it, in Map or hashmap, value is stored in the form of Key & Value pair. In this article i will try to demonstrate the same.
Syntax to define map –> Map mapA = new HashMap();
How to add value in map? –> mapA.put(“key1”, “element 1”);
How to get value from map? –> Object value = mapA.get(key);
–> Value from map can also be retrived by using Iterator. Shown in above screenshot.
Now, how to use Map to with TestNG Dataprovider in Data Driven Testing?
Let us suppose my Test data file is located at: C://Users//Prakash//Desktop//TestData.xlsx & it looks as shown in below image –
Now, our task is to pass value from row 2 onward to our test case using Map. Have a look on below Selenium Java code –
package demoPackage1;
import java.io.File;
import java.io.FileInputStream;
import java.io.IOException;
import java.util.HashMap;
import java.util.Map;
import org.apache.poi.xssf.usermodel.XSSFSheet;
import org.apache.poi.xssf.usermodel.XSSFWorkbook;
import org.testng.annotations.DataProvider;
import org.testng.annotations.Test;
public class Testclass {
@Test(dataProvider = "data")
public void integrationTest(Map<Object, Object> map) {
System.out.println("-------------Test case started ----------------");
System.out.println(map.get("UserName"));
System.out.println(map.get("Password"));
System.out.println(map.get("DoB"));
System.out.println("-------------Test case Ended ----------------");
}
@DataProvider(name = "data")
public Object[][] dataSupplier() throws IOException {
File file = new File("C://Users//Prakash//Desktop//TestData.xlsx");
FileInputStream fis = new FileInputStream(file);
XSSFWorkbook wb = new XSSFWorkbook(fis);
XSSFSheet sheet = wb.getSheetAt(0);
wb.close();
int lastRowNum = sheet.getLastRowNum() ;
int lastCellNum = sheet.getRow(0).getLastCellNum();
Object[][] obj = new Object[lastRowNum][1];
for (int i = 0; i < lastRowNum; i++) {
Map<Object, Object> datamap = new HashMap<>();
for (int j = 0; j < lastCellNum; j++) {
datamap.put(sheet.getRow(0).getCell(j).toString(), sheet.getRow(i+1).getCell(j).toString());
}
obj[i][0] = datamap;
}
return obj;
}
}
Once you run above test case, Console output will looks like –
[TestNG] Running:
C:\Users\Prakash\AppData\Local\Temp\testng-eclipse-1161438956\testng-customsuite.xml
-------------Test case started ----------------
user1
pass1
dob1
-------------Test case Ended ----------------
-------------Test case started ----------------
user2
pass2
dob2
-------------Test case Ended ----------------
-------------Test case started ----------------
user3
pass3
dob3
-------------Test case Ended ----------------
PASSED: integrationTest({UserName=user1, DoB=dob1, Password=pass1})
PASSED: integrationTest({UserName=user2, DoB=dob2, Password=pass2})
PASSED: integrationTest({UserName=user3, DoB=dob3, Password=pass3})
===============================================
Default test
Tests run: 3, Failures: 0, Skips: 0
===============================================
===============================================
Default suite
Total tests run: 3, Failures: 0, Skips: 0
===============================================
[TestNG] Time taken by org.testng.reporters.SuiteHTMLReporter@7c30a502: 47 ms
[TestNG] Time taken by org.testng.reporters.EmailableReporter2@7e0ea639: 15 ms
[TestNG] Time taken by org.testng.reporters.jq.Main@3ac3fd8b: 47 ms
[TestNG] Time taken by org.testng.reporters.JUnitReportReporter@71be98f5: 16 ms
[TestNG] Time taken by org.testng.reporters.XMLReporter@511baa65: 15 ms
[TestNG] Time taken by [FailedReporter passed=0 failed=0 skipped=0]: 0 ms
In Above Console O/P you can clearly see that, test case has been run 3 times with 3 set of test data & is taken from Excel sheet using testNG DataProvider.
Refer below video to understand more about How to use map and hashmap along with testng dataprovider –
Hope above example helps !!!
For more about Test Automation Framework, refer below links –
Before we start we Keyword driven framework in selenium, let us try to understand what is framework.
What is Framework?
In a very simple language, it is a structure and design which help others to write test cases easily by using re-usability, readability, maintainability
What is Keyword driven framework?
in KDF, every action which we perform on the UI elements is been written in terms of keywords. These keywords will define what action should be taken on UI.
Advantages of Keyword Driven Framework –
Since all test cases are in excel file, it is very easy to know which test cases are covered for non technical person as well. It helps great for writing detailed test plan because you can show in excel sheet what and all you are going to cover.
Less technical knowledge required once framework is setup. Once framework is set, manual tester can even use the keywords and write test cases.
Easy to understand since it is well structured.
code re-usability
Automation test case preparation can start early during development phase.
Before we start with data driven framework, let us understand few important things.
Why not to hard code in Test Automation Framework?
–>Let us take an example of testing web application. In actual, you may need to run test cases in various environments like Unit Testing, System Testing, System Integration Testing, UAT & can be in Production. So for all these regions, URL will be different, username and password can be different. So if you are hard coding these things, you need to change them for each environment. So its not good practice to hard code the things which are used at multiple places.
Data Driven Framework:
It is nothing but to execute one test case with multiple set of data, with multiple conditions. When you wanted to execute similar flow (let us say account opening procedure) with various data combinations, it is not good idea to create separate test case for each data set, so this is how data driven frameworks came in to picture.
Components of Data Driven Framework:
Create a folder Structure for your framework, refer below screenshot in which i have shown a sample folder structure for data driven framework.
1. Package for Page Object –>
This package will contain all page object. For each page there should be one class containing all objects / web-elements from that page. This helps to keep changing web-element away from our actual test cases. This is to achieve Page Object Model (POM) in our Test Automation Framework.
2. Package for Properties file –>
This package will contain all properties file to store data like URL, credentials & other. So that any changes in dynamic parameters like URL, username, passwords need not to change the values in code. Just change in these properties file, should update it in all test cases.
3. Package to keep Test Data –>
This package is to keep test data of data driven testing. This data can be kept in excel file format. Apache POI / JXL api can be used to read this data & use it for test cases during execution. Test data can also be kept in notepad, any database. But preferred one is Excel.
4. Package to write actual Test Cases –>
In a framework, code for actual test cases should be isolated from other commonly used methods & files. So this package is to write the actual test cases. Other classes from other packages can be called while writing test cases.
5. Utilities used for framework –>
As i said above, in framework, only actual test cases should be kept in one package & rest other common methods should be kept in another one. This utilities package will contain all common methods that are required for Test Automation Framework. For Example – Take Screenshot, logging, common skeleton to launch driver, listeners, reporters etc.
6. Create one folder to keep all jar files (If you are not using Maven in your project)
7. Create one folder to store log information (with the help of log4j & listeners)
Now, refer the below code from each of the module for complete Data Driven Framework
Step 1: Create the folder structure as shown above. Step2: Create config.properties file in propFiles package, refer below properties file
Step3: Create Log4j.properties file under src folder which is used for logging information. Refer below code for log4j.properties
// Here we have defined root logger
log4j.rootLogger=ALL,CONSOLE,R
// Here we define the appender
log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
log4j.appender.R=org.apache.log4j.RollingFileAppender
log4j.appender.dest1=org.apache.log4j.RollingFileAppender
log4j.appender.dest1.maxFileSize=5000KB
log4j.appender.dest1.maxBackupIndex=3
// Here we define log file location
log4j.appender.R.File=./log/testlog.log
// Here we define the layout and pattern
log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern= %5p [%t] (%F:%L)- %m%n
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern=%d - %c -%p - %m%n
Step4: Identify and write page objects which you require for your test case. This will achieve Page Object Model (POM). For my sample example, i have identified objects for login test case. Refer below objects. HomePageObjects:
package com.demowebshop.pageObjects;
import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
public class HomePage {
public static String LoginLinkXpath = "//a[@class='ico-login']";
public static WebElement LoginLinkWebElement(WebDriver driver){
return driver.findElement(By.xpath(LoginLinkXpath));
}
}
LoginPageObject:
package com.demowebshop.pageObjects;
import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
public class LoginPage {
public static String EmailFieldXpath = "//input[@id='Email']";
public static String PasswordFieldXpath = "//input[@id='Password']";
public static String LoginButtonXpath = "//input[@class='button-1 login-button']";
public static WebElement EmailFieldWebElement(WebDriver driver){
return driver.findElement(By.xpath(EmailFieldXpath));
}
public static WebElement PasswordFieldWebElement(WebDriver driver){
return driver.findElement(By.xpath(PasswordFieldXpath));
}
public static WebElement LoginButtonWebElement(WebDriver driver){
return driver.findElement(By.xpath(LoginButtonXpath));
}
}
Step5: Now, its time to write utilities.
First one is to read properties file. Data stored in properties file like URL, browser & other need to be used in test cases. So below class will help to read properties file.
package com.demowebshop.utilities;
import java.io.File;
import java.io.FileInputStream;
import java.io.FileNotFoundException;
import java.io.IOException;
import java.util.Properties;
public class ReadPropertiesFile {
Properties prop = new Properties();
String filePath = "C://Users//Prakash//workspace//ddf//src//com//demowebshop//propFiles//config.properties";
public String ReadPropertiesFileByKey(String key) throws FileNotFoundException{
File file = new File(filePath);
FileInputStream fis = new FileInputStream(file);
try {
prop.load(fis);
} catch (IOException e) {
e.printStackTrace();
}
return prop.getProperty(key);
}
}
Now, once we get browser value from properties file, select the browser using below class
package com.demowebshop.utilities;
import org.apache.log4j.Logger;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
import org.openqa.selenium.firefox.FirefoxDriver;
import org.openqa.selenium.ie.InternetExplorerDriver;
public class SelectBrowser {
Logger log = Logger.getLogger("BrowserSelection");
public WebDriver selectBrowser() throws Exception {
ReadPropertiesFile prop = new ReadPropertiesFile();
WebDriver driver = null;
String browser = prop.ReadPropertiesFileByKey("browser");
while (browser == null) {
log.fatal("Browser is not specified in Configuration file. Terminating process !!!");
System.exit(0);
}
if (browser.equalsIgnoreCase("firefox")) {
driver = new FirefoxDriver();
log.info("Browser selected for testing is : Mozilla Firefox");
} else if (browser.equalsIgnoreCase("chrome")) {
System.setProperty("webdriver.chrome.driver", "C:\\chromedriver.exe");
driver = new ChromeDriver();
log.info("Browser selected for testing is : Google Chrome");
} else if (browser.equalsIgnoreCase("ie")) {
System.setProperty("webdriver.ie.driver", "C:\\IEDriverServer.exe");
driver = new InternetExplorerDriver();
log.info("Browser selected for testing is : Internet Explorer");
} else {
log.fatal("Selected browser value should be either firefox or chrome or ie --> Update in Configuration file is required");
System.exit(0);
}
return driver;
}
}
Since we are using data driven testing, our test data is stored in excel file. This excel file need to read & process the test cases based on test data. Use below class to read excel file –
package com.demowebshop.utilities;
import java.io.File;
import java.io.FileInputStream;
import java.io.FileNotFoundException;
import org.apache.poi.xssf.usermodel.XSSFRow;
import org.apache.poi.xssf.usermodel.XSSFSheet;
import org.apache.poi.xssf.usermodel.XSSFWorkbook;
import org.testng.log4testng.Logger;
public class ExcelReader {
static ReadPropertiesFile prop = new ReadPropertiesFile();
Logger log = Logger.getLogger(ExcelReader.class);
static FileInputStream fis = null;
public FileInputStream getFileInputStream() throws FileNotFoundException{
String filepath = prop.ReadPropertiesFileByKey("filepath");
File srcfile = new File(filepath);
try {
fis = new FileInputStream(srcfile);
} catch (FileNotFoundException e) {
log.fatal("TestData File is not found. terminating process !!! Check Configuration file for file path of TestData file");
System.exit(0);
}
return fis;
}
public Object[][] getExceData() throws Exception{
fis = getFileInputStream();
XSSFWorkbook wb = new XSSFWorkbook(fis);
XSSFSheet sheet = wb.getSheetAt(0);
int TotalNumberOfRows = (sheet.getLastRowNum()+1);
int TotalNumberOfCols =2;
String[][] arrayExcelData = new String[TotalNumberOfRows][TotalNumberOfCols];
for (int i = 0; i<TotalNumberOfRows; i++){
for (int j=0; j<TotalNumberOfCols; j++){
XSSFRow row = sheet.getRow(i);
// String cellData = row.getCell(j).toString();
arrayExcelData[i][j] = row.getCell(j).toString();
}
}
wb.close();
return arrayExcelData;
}
}
Its time to create a common skeleton (to use driver from another class, which will be common for @BeforeMethod and @AfterMethod annotation. Refer below code –
package com.demowebshop.utilities;
import java.util.concurrent.TimeUnit;
import org.openqa.selenium.WebDriver;
import org.testng.annotations.AfterMethod;
import org.testng.annotations.BeforeMethod;
public class BaseTest {
SelectBrowser select = new SelectBrowser();
ReadPropertiesFile prop = new ReadPropertiesFile();
protected WebDriver driver = null;
@BeforeMethod
public void launchBrowser() throws Exception{
String url = prop.ReadPropertiesFileByKey("URL");
driver = select.selectBrowser();
driver.navigate().to(url);
driver.manage().timeouts().implicitlyWait(10, TimeUnit.SECONDS);
driver.manage().window().maximize();
}
@AfterMethod
public void closeBrowser(){
driver.close();
driver.quit();
}
}
Once all this is done, Its time to write actual test. Use dataprovide annotation to pass the data which we read it from excel reader.
I am using demowebshop.tricentis.com & its login functionality to demonstrate.
Refer below code –
package com.demowebshop.Tests;
import org.testng.annotations.DataProvider;
import org.testng.annotations.Test;
import com.demowebshop.pageObjects.HomePage;
import com.demowebshop.pageObjects.LoginPage;
import com.demowebshop.utilities.BaseTest;
import com.demowebshop.utilities.ExcelReader;
public class LoginTest extends BaseTest{
@Test(dataProvider = "TestData1")
public void LoginTestCase( String username, String password){
System.out.println(username);
System.out.println(password);
HomePage.LoginLinkWebElement(driver).click();
LoginPage.EmailFieldWebElement(driver).sendKeys(username);
LoginPage.PasswordFieldWebElement(driver).sendKeys(password);
System.out.println(driver.getTitle());
}
@DataProvider(name = "TestData1")
public Object[][] LoginTestData() throws Exception{
ExcelReader ER = new ExcelReader();
return ER.getExceData();
}
}
Once this is done, Update your test data file (for Data Driven Framework) with your username and passwords, as shown below –
Now, you are good to run Test. Right click on your actual test case, Run it as TestNG Test.
You should good results.
To learn how the same can be achieved using Map and HashMap, refer –
Integration of Selenium test case with TestNG Framework helps in many aspects such as better reporting, organizing test cases in better way & many other.
Working on Input Text Box and buttons is a very first step of selenium. We use sendKeys method to send value to text box where as click / submit method to click on button.