In this blog, we will learn how to capture webelement screenshot using selenium. Till Selenium 3 we have an option that to take the screenshot for an entire webpage. From selenium 4 onwards they have introduced an option that to capture a webelement. Previously, using some third party libraries like Ashot, shutterbug to capture the webelemet or webpage.

Pre-requisites:

1. Add the selenium-4-alpha.jar file in your project or add the corresponding dependency is yours is a Maven project
2. in your class file, inspect the target element and store it in a webelement.
3. Now, use the regular screenshot logic method and store the value in a folder using Filehandler method.
4. Instead of driver, use the webelement reference variable to capture the screenshot of the target element instead of full webpage.

package Basics;

import java.io.File;

import org.openqa.selenium.By;
import org.openqa.selenium.OutputType;
import org.openqa.selenium.TakesScreenshot;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import org.openqa.selenium.chrome.ChromeDriver;
import org.openqa.selenium.io.FileHandler;

public class CaptureWebelementScreenshot {

public static void main(String[] args) throws Exception {
// TODO Auto-generated method stub
WebDriver driver;
System.setProperty("webdriver.chrome.driver", "E:\\Selenium-Softwares\\chromedriver.exe");
//System.setProperty("webdriver.gecko.driver", "E:\\Selenium-Softwares\\geckodriver.exe");
driver=new ChromeDriver();
driver.get("http://demo.automationtesting.in/Register.html");
Thread.sleep(3000);
WebElement element = driver.findElement(By.id("imagetrgt"));

File source = ((TakesScreenshot)element).getScreenshotAs(OutputType.FILE);
FileHandler.copy(source, new File("./screenshots/element.png"));
Thread.sleep(3000);
driver.quit();

}

}

Please watch the Youtube video for better understanding.

The post How to Capture WebElement Screenshot in Selenium Webdriver using selenium 4 appeared first on Selenium Webdriver Appium Complete Tutorial.

In Many Real time scenarios, When we click on a link we see many of those opens in new tab or new windows. We generally use the switchtowindow concept from selenium and handle it. We need to be cautious while switching window and we should always switch back the driver focus to the old window when we need to handle the operation on the parent window. Please click this link for the example.

However, We can handle it in a different way to open the link in the same tab. We use JavaScriptExecutor to alter attributes for the DOM and we open the link in the same tab. Using JavaScriptExecutor we alter target attribute value and then we click on the link. Which makes links open in the same Tab. For navigation to back window we use navigate commands in selenium. This is a pretty easy way to handle different screens originating from the same application.




Sample Code:

import io.github.bonigarcia.wdm.WebDriverManager;
import org.openqa.selenium.By;
import org.openqa.selenium.JavascriptExecutor;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import org.openqa.selenium.chrome.ChromeDriver;

public class AvoidSwitchToWindow {

    public static void main(String[] args) {

        WebDriverManager.chromedriver().setup();
        WebDriver driver = new ChromeDriver();

        driver.get("http://demo.automationtesting.in/Windows.html");

        String mainWindowTitle = driver.getTitle();
        System.out.println("Main Window Title is: "+mainWindowTitle);

        WebElement we = driver.findElement(By.cssSelector("a[href='http://www.sakinalium.in']"));

        JavascriptExecutor js = (JavascriptExecutor)driver;
        js.executeScript("arguments[0].setAttribute('target','_self');",we);

        we.click();

        String childWindowTitle = driver.getTitle();
        System.out.println("Child Window Title is: "+childWindowTitle);

        driver.navigate().back();

        mainWindowTitle = driver.getTitle();
        System.out.println("Main Window Title is: "+mainWindowTitle);
    }
}

In the above program, we changed the target attribute from _blank to _self. So, the new window will open in the same window instead of a new window.

Please watch the YouTube video for better understanding.

The post How to Avoid Switch To Window in Selenium WebDriver appeared first on Selenium Webdriver Appium Complete Tutorial.

After selenium 3, We got habituated to download exe files like chrome.exe, geckodriver.exe etc. to launch browsers. All these executable files are standalone server executable files that implements JSON-wire protocol and works as a glue between the test script and Browsers.

Most often, when we have updates of our browser, we have to update exe files as well to implement JSON-wire Protocol. So, All the time We need download updated EXE files and we need to update our repository.

We have an alternate to escape from those hurdles with Webdriver Manager Library.

Web Driver Manager Reference Link:

https://github.com/bonigarcia/webdrivermanager




Advantages of WebdriverManager :

1. No need to download the chrome.exe,geckodriver.exe files etc..
2. No need to set driver exe file path in selenium program
3. No need to bother about the latest version of browser and exe files
4. So, no issues with browser updates and exe files

To start with it, add below maven dependency or download jar files from here:

 
<dependency>
    <groupId>io.github.bonigarcia</groupId>
    <artifactId>webdrivermanager</artifactId>
    <version>3.0.0</version>
    <scope>test</scope>
</dependency>

Syntax:

WebDriverManager.chromedriver().setup();

Above syntax will download chromedriver exe file in run time during your program. For first time it takes a while to launch your browser.

Sample Program:

public class WebDriverManagerDemo
 {
	public static void main(String[] args)
    {
		WebDriverManager.chromedriver().setup();
		WebDriver driver = new ChromeDriver();
		driver.get("https://automationtesting.in");
	}
}

Is it possible to Download Particular version of Browser using WebDriverManager?

Yes, it’s possible to download particular version using Webdrivermanager.

Syntax:

1. chromedriver().version(“2.26”).setup()

•  Above syntax will download 2.26 version of chrome driver.

2. firefoxdriver().arch32().setup()

• Using Above syntax you will be able to download 32 bit Firefox driver.

Sample Program with ChromeDriver Version 2.26:

 
public class WebDriverManagerDemo
 {
	public static void main(String[] args) 
    {
		WebDriverManager.chromedriver().version("2.26").setup();
		WebDriver driver = new ChromeDriver();
		driver.get("https://automationtesting.in");
	}
}

Above program will download the 2.26 version of chromedriver exe file and used the same to launch the browser.

Please watch YouTube video for better understanding.

– This blog written by SUBBARAYUDU DARISIPUDI.

The post No More Driver EXE files for Selenium Execution – Instead Use WebDriverManager appeared first on Selenium Webdriver Appium Complete Tutorial.

Handling textboxes in selenium will discuss about how to handle textboxes on a webpage. Basically a textbox is an input tag and will accept character sequence. While automating any application if you want to automate any textbox in selenium you have two types of options to enter data into the textbox. One is using sendKeys() method of selenium webdriver and another is using JavaScriptExecutor.

While entering into the data we need to remember some of the points:

1. You need to use sendKeys() method to enter data into textbox after identifying the webelement on the webpage.
2. If already a textbox contains data in it and you try to enter the data into same textbox then the data will be appended to the existing data.
3. If you want to enter the data which is already having data in it. Then you need to clear the textbox before entering data into it.
4. To clear the textbox we can use clear() method of selenium.
5. Sometimes selenium methods will not work and not able to identify the elements and not able to enter data into it. Then we can take the help of JavaScriptExecutor to enter data into the textbox.

Now will see the examples for the above statements:

1. Use sendKeys() method to enter the data into textbox.

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

public class HandleTextbox {
    
    @Test
    public void textBox()
    {
        System.setProperty("webdriver.gecko.driver", "/KRISHNA VOLUME/drivers/geckodriver");
        WebDriver driver = new FirefoxDriver();
        driver.get("http://demo.automationtesting.in/Register.html");
        driver.findElement(By.xpath("//*[@id='basicBootstrapForm']/div[1]/div[1]/input")).sendKeys("Krishna");        
    }
}

2. Append data in a Textbox.

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

public class HandleTextbox {
    
    @Test
    public void textBox()
    {
        System.setProperty("webdriver.gecko.driver", "/KRISHNA VOLUME/drivers/geckodriver");
        WebDriver driver = new FirefoxDriver();
        driver.get("http://demo.automationtesting.in/Register.html");
        driver.findElement(By.xpath("//*[@id='basicBootstrapForm']/div[1]/div[1]/input")).sendKeys("Krishna");
        driver.findElement(By.xpath("//*[@id='basicBootstrapForm']/div[1]/div[1]/input")).sendKeys("Sakinala");
    }
}

3. Clear the Textbox using clear() method.

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

public class HandleTextbox {
    
    @Test
    public void textBox()
    {
        System.setProperty("webdriver.gecko.driver", "/KRISHNA VOLUME/drivers/geckodriver");
        WebDriver driver = new FirefoxDriver();
        driver.get("http://demo.automationtesting.in/Register.html");
        driver.findElement(By.xpath("//*[@id='basicBootstrapForm']/div[1]/div[1]/input")).sendKeys("Krishna");
        driver.findElement(By.xpath("//*[@id='basicBootstrapForm']/div[1]/div[1]/input")).clear();
    }
}

4. JavaScriptExecutor to enter data into textbox.

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

public class HandleTextbox {
    
    @Test
    public void textBox()
    {
        System.setProperty("webdriver.gecko.driver", "/KRISHNA VOLUME/drivers/geckodriver");
        WebDriver driver = new FirefoxDriver();
        driver.get("http://demo.automationtesting.in/Register.html");
        JavascriptExecutor js = (JavascriptExecutor)driver;        
        js.executeScript("document.querySelector(\"input[placeholder='First Name']\").value='Krishna'");
    }
}

This way we can handle textboxes while automating the application using selenium webdriver.

Please watch YouTube video for better understanding.

The post Handling Textboxes in Selenium appeared first on Selenium Webdriver Appium Complete Tutorial.

JavaScriptExecutor is one of the interfaces in selenium. The basic advantage of JavaScriptExecutor is it provides a way to execute JavaScript in Selenium Webdriver. Sometimes locators may not work, in that case JavaScriptExecutor will helps to interact with the web elements on the particular webpage.  The reason behind this is; even selenium webdriver internally converts language bindings into its equivalent JavaScript and injects into the respective browser. JavaScriptExecutor is also very useful to identify and interact with the hidden and disabled elements on the webpage.

As JavaScriptExecutor is an interface so we can not create an object to this, for this we will type caste to driver object using below syntax:

JavascriptExecutor js = (JavascriptExecutor)driver;
js.executeScript(javaScript, arguments);

Now we will see some of the examples below that how we can use JavaScriptExecutor to execute the JavaScript to interact with the web elements.

1. How to enter value into textbox:

JavascriptExecutor js = (JavascriptExecutor)driver;
js.executeScript("document.getElementById('email').value='krishna@gmail.com'");

2. How to click a button:

JavascriptExecutor js = (JavascriptExecutor)driver;
js.executeScript("document.querySelector('#enterimg').click()");

3. How to refresh a window:

JavascriptExecutor js = (JavascriptExecutor)driver;
js.executeScript("history.go(0)");

4. How to get the text of a particular web element:

JavascriptExecutor js = (JavascriptExecutor)driver;
String text = js.executeScript("return document.getElementById('btn2').innerHTML").toString();
System.out.println("WebElement Text is : "+ text);

5. How to get the title of the WebPage:

JavascriptExecutor js = (JavascriptExecutor)driver;
String text = js.executeScript("return document.title").toString();
System.out.println("Page Title is : "+ text);

6. How to scroll vertically for certain pixels:

JavascriptExecutor js = (JavascriptExecutor)driver;
js.executeScript("window.scrollBy(0,500)");

The above code vertically scrolls 500 pixels towards down.

7. How to scroll till the bottom of the web page:

JavascriptExecutor js = (JavascriptExecutor)driver;
js.executeScript("window.scrollTo(0, document.body.scrollHeight)");

8. How to scroll to a particular element:

JavascriptExecutor js = (JavascriptExecutor)driver;
js.executeScript("document.querySelector('#countries').scrollIntoView()");

9. How to navigate back to page:

JavascriptExecutor js = (JavascriptExecutor)driver;
js.executeScript("window.history.back()");

10. How to navigate to next page:

JavascriptExecutor js = (JavascriptExecutor)driver;
js.executeScript("window.history.forward()");

This way we can JavaScriptExecutor to perform certain actions on a webpage if the normal selenium webdriver methods are not working.

Please watch YouTube video for better understanding.

The post JavaScriptExecutor in Selenium appeared first on Selenium Webdriver Appium Complete Tutorial.

Below are the causes to face this exception:

Thrown to indicate that although an element is present on the DOM, it is not visible, and so is not able to be interacted with. To overcome this kind of situation we need to use synchronization concept in selenium. So, add an explicit wait to wait for the correct conditions to be met before trying to interact with the element. We have an option to use wait in so many ways or conditions. Will make use of all those things depends on the situation and will try to resolve or handle these type of scenarios.

Sometimes if the element is there on the web page and not in the visible area then also you can find this type of exception. To overcome this situation we need to scroll to that particular web element first then you can interact with that element to resolve this type of exception. Most of the times selenium webdriver will take care of this situation that it will find the element which is not there on the visible area and it will interact with that element. But some times, if the situation comes, then we need to scroll to the particular web element or scroll in the webpage and then can interact with the required element.

This way we can overcome the ElementNotVisibleException in selenium webdriver.

Please watch the YouTube video for this blog for better understanding.

The post Selenium ElementNotVisibleException appeared first on Selenium Webdriver Appium Complete Tutorial.

Below are the causes to face this exception:

1. This exception is caused because the list of windows hold by the driver.getWindowHandles() method is not up to date. One of the windows that previously existed is no longer exists; so, you can not switch to that window. To handle this we need to make sure that you are not closing a window without refreshing the available list of windows using this method.
2. The other reason behind this exception is that you may trying to switch to window before handling all the opened windows using driver.getWindowHandles() method. And we need to keep in mind that we should know which window we are trying to switch as getWindowHandles() holds all the windows which are opened. To get the main window then you can use one the webdriver methods called “driver.getWindowHandle()”. Once you have all the windows with you then you can loop through all the windows which are there in the list and we can switch to the desired window.

Once you done with your work, then you need to come to the parent or default windows then only your execution will be smooth. This way can overcome the NoSuchWindowException in selenium webdriver.

Please watch the YouTube video for this blog for better understanding.

The post Selenium NoSuchWindowException appeared first on Selenium Webdriver Appium Complete Tutorial.

Below are the causes to face this exception:

1. Let’s assume in your application if you have a frame and it contains some elements (for example we will take a textbox in this scenarios) and you want to enter something into that textbox. For this we have captured the locator of the textbox and used the same in the code and everything is correct as per the logic. But after execution of the script we will find NoSuchFrameException. And best part here is selenium will tell us with the proper exception, instead if it says NoSuchElementException then it will be very difficult us to resolve these kind of scenarios.Actually the issue is, if you have frames in your application then you need to switch to that frame first and then only you will be able to interact with the elements which are there inside the frame in selenium.
2. Let’s assume one more scenario where you have a webpage with more than one frame. We will call them frame A and frame B. We will assume that we first switched to frame B to check/verify something in the frame B. If we then try to find frame A, we will get NoSuchFrameException. This is because frame A does not exist in the context of frame B.

To overcome this issue is to always go back to the parent frame before trying to switch to another frame

If you have a frame inside a frame then you no need to go back to parent content. You can directly switch to that frame. But after completion of all the things which you want to perform inside the frames need to come out of the frames to continue further script capturing and execution.

You can use frame IDs or WebElements to locate the frames and then you can switch to them. You can also use frame indexes to switch to them but use this as a last option.

Please watch the YouTube video for this blog for better understanding.

The post Selenium NoSuchFrameException appeared first on Selenium Webdriver Appium Complete Tutorial.

Below are the reasons to get this exception:

1. The locator which you are using to locate the element is incorrect/changed.
2. The element which you are looking is not rendered.
3. Trying to find the element before it was rendered.

Locator is Incorrect/changed:

Here we have two possibilities that the locator which you have written to identify an element may be incorrect or sometimes after writing/capturing the code, if there are any changes in the application then the locator may change. In both scenarios tool will not able to identify the element and it will throw NoSuchElementException.

To overcome this, we need to take the element locator which is causing this issue and validate against the application that the locator is identifying/highlighting any element on the application or not? For this we can use Firefox add-ons i.e. firebug and firepath then you place the locator in the firepath and validate the same against application that it is highlighting the element or not?

And sometimes if you are not navigated to a particular page after clicking on a link or button then it will cause this issue as it will look for the element to interact in the new page but actually it is not navigated to that page. But here the actual error show that it is not able to find particular element but the issue is not with that element as the page not yet navigated to that page. This kind of situation is bit tricky, but we need to find these type of issues also. Best example for this is navigating to application using login page but if the credentials are wrong then you might get this issue.

To overcome this issue, we can capture the screenshots for these type of scenarios and can find the issues by looking into these screenshots.

Element Not Rendered:

It is bit difficult to find this as something is not rendering on the application then you need to debug the code and see what could be the real issue. If something is not rendering then that is a bug in the application.

Here if you use the first issue resolution then it will not work as if you try to highlight the element in the application using firebug and firepath then it will not show anything in the console. But this is not an issue with the locator instead the element is not rendering on the application.

To overcome this issue, we can capture the screenshots for these type of scenarios and can find the issues by looking into these screenshots.




Trying to find the element before it was rendered:

Sometimes we are trying to interact with an element which is not yet rendered on the application. Here also we will get the same kind of issue which we saw in the above. But in the above case the element is not completely rendering, here it is rendering but taking bit more time to load. Now a days lots of modern websites use technologies such as jQuery or AngularJS, which use the JavaScript to manipulate the DOM. And Our Selenium is very fast. In many cases, it’s ready to start interacting with your website before the JavaScript has finished doing its job.

To overcome this, we need to think that how a manual tester will test these kind of scenarios. They will wait until the element renders on the application. So, same way we need to wait to load that particular element. For this we will use Synchronization concept i.e. we need to stop the code execution until the element renders. For this we can use ExpectedConditions class and its methods to achieve this functionality.

Please watch the YouTube video for this blog for better understanding.

The post Selenium NoSuchElementException appeared first on Selenium Webdriver Appium Complete Tutorial.

One of the good things in selenium is while looking into the exception we will come to know what went wrong as the exception names will give some what clear picture for the error which we will face.

Below are some of the Exceptions which we will see while automating the applications:

1. NoSuchElementException
2. NoSuchFrameException
3. NoSuchWindowException
4. ElementNotVisibleException
5. StaleElementReferenceException
6. InvalidElementStateException
7. UnreachableBrowserException
8. SessionNotFoundException

Now we will see briefly about these exceptions:

NoSuchElementException:

This is the most and frequent facing exception. You will definitely find this kind of exception while automating the application. The reason for this exception is, the element you are trying to find does not exist.

NoSuchFrameException:

This is also most and frequent facing exception. In modern applications people are using iFrames very frequently. When you try to find an iFrame on application and it is not exist in the application then code will throw NoSuchFrameException.

NoSuchWindowException:

This is also very similar to the previous exception. A Window is a browser which is opened by the webdriver or child window(i.e.another browser opened from the parent browser). When you try find a Window and that is not available at present, then the code will throw NoSuchWindowException.

ElementNotVisibleException:

This is also most and very frequent facing exception. This ElementNotVisibleException tells you that the WebElement that you are trying to interact with is not visible to the user.

StaleElementReferenceException:

This is an exception that you will quite often see when you work with AJAX or heavy JavaScript websites, where the DOM is continually being changed. When the element is no longer attached to the DOM then you will face this exception.

InvalidElementStateException:

This exception you can not find very frequently. When you try to interact with any element then an unexpected popup will come but we are not sure why and what it is. An InvalidElementStateException is thrown when the WebElement that you are trying to interact with is not in a state that would allow you to perform the action that you would like to perform.

UnreachableBrowserException:

Sometimes you will face this type of Exception. As we know that selenium sends commands to the browser to execute and get the response back. Sometimes we will not get the response from the browser then we will get UnreachableBrowserException.

SessionNotFoundException:

You will not get this kind of exception frequently. But while you executing your tests and something will go wrong and will lose connection with the browser instance that you are driving. Then you will get SessionNotFoundException.

These are the most frequently exceptions we will face while automating any kind of application.

Please watch the YouTube video for this blog for better understanding.

The post Selenium WebDriver Exceptions appeared first on Selenium Webdriver Appium Complete Tutorial.