Selenium: First webdriver script with Java


Till now we have gone through all the rudimentary fundamentals of the Java OOPs and Interface. Its time to start writing automation scripts in Selenium with Java.

In this blogs, we will focus only on selenium webdriver as it is widely used automation component of selenium and  all other selenium components are obsolete now. We will start from writing some basic scripts and eventually we will cover all other advance stuffs of selenium. Lets begin !!

We will automate our google search task here as it is the most common thing we do in our daily routine.(isn't it ?)


package blog;

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


@SuppressWarnings("unused")
public class googleSearch {

public static void main(String[] args) {

WebDriver driver;

System.setProperty("webdriver.chrome.driver","C:\\Program Files\\chromedriver.exe");
driver=new ChromeDriver();
driver.get("https://www.google.com");
Thread.sleep(1000);
driver.manage().window().maximize();

WebElement search=driver.findElement(By.id("lst-ib"));
search.sendKeys("India");

Thread.sleep(3000);

WebElement btn=driver.findElement(By.className("lsb"));
btn.click();
Thread.sleep(3000);

 driver.close();

}
}



[Source: www.google.com ]



Explanation:

We are creating one package called 'blog' in eclipse and we will include all our automation scripts in that package.

In this code, first we are importing all the necessary selenium packages which are added as external jars in our build path in eclipse. As I am using chrome browser here I have imported jars for chrome. Similarly, you can import jars according to which browser you are using. You can download jars from here.

Then we are creating and instantiating webdriver object with google chrome driver. we need to store .exe files of browsers in our location and provide path of the same while setting the system properties of browser.

driver.get() command is used to open the particular URL and with driver.manage functions we can customize browser properties.

Next and important part is to search all the web elements on which we will work. As for google search we write our content in search bar. So, we need to find that web element using one of its developer properties. It can be id, class name, css selector, xpath or any other. Here, we are finding web element using its id and sending our search query to search bar using sendkeys command.

Then we need to click on button 'Google Search' and after defining web element btn for that in this code, we can click on it using btn.click() command.

In our code, I have mentioned Thread.sleep(3000) which is actually a wait time, it is in ms and it can be according to requirements. It is necessary because may be sometimes web page may render slowly and our driver may not be able to find particular web element on page and eventually it will lead to 'element not found' exception. 

With driver.close() command, we are closing the browser. We will see more functions, locators and commands in coming posts.

Till then just like this, try to automate your daily web surfing !! 

Cheers !










Comments

Post a Comment

More posts on selenium...

Selenium: Automate Web Application Login

Image
From last post, we have started writing basic selenium automation scripts. Now, let's take that journey forward and try to automate any web based application.  In this post, we will automate our Facebook login as a demo which can be used for any web based application with little modifications. [Source: www.facebook.com ] Code with Explanation:  We will create one class named FacebookLogin in the package blog in eclipse which we have created during googleSearch automation script. package blog; Here, we will import all the necessary external jars, we can give suppress warnings for jar which we are not using. import static org.junit.Assert.*; import org.junit.After; import org.junit.Before; import org.junit.Test; import org.openqa.selenium.By; import org.openqa.selenium.WebDriver; import org.openqa.selenium.WebElement; import org.openqa.selenium.chrome.ChromeDriver; @SuppressWarnings("unused") public class FacebookLogin {...
Read more

Selenium: BDD Cucumber- Cucumber Options

Image
In last post, we learnt how to write features, scenarios and how to execute BDD cucumber tests. As we are implementing our BDD framework using cucumber, let's explore further about cucumber. We will start with various cucumber options in this post. We run our cucumber tests from Runner class. You can just go through this once to recapitulate things we discussed in last post  Cucumber Demo Test  . In that runner class, we have different cucumber options, it is just like a settings page that how we want to run our tests and different options are also available for that purpose. [Cucumber Options] Dry Run:   dryrun can be true or false. If dryrun is set true, it will check if the steps written in feature file has corresponding code in step definition file or not. It is good option to catch rudimentary errors. The default value of dryrun is false. You can just try with dryrun=true option to see the result. Monochrome: monochrome option also can ta...
Read more

Selenium: All about XPath Locator in WebDriver

Image
As we have started writing simple web application login like scripts, its time to move one step ahead. Till now we were finding web elements using general locators like id, name, classname etc. but sometimes it is difficult to find elements using these locators. What if elements don't have these locators, What if some elements are dynamically changing, to answer all these questions, we have Xpath . Xpath is used to find complex and dynamically changing web elements of the web page. It is defined as XML path, it is basically a syntax for finding web element using its XML path expression. It takes advantage of HTML DOM structure while finding web elements.  Syntax: Xpath= //tagname[@attribute='value'] // : current node tagname : name of the tags like input, a, img, label etc. attribute : name of the attributes like id, name, classname etc. value : value of that particular attribute There are mainly two types of Xpath. Absolute Xpath:  Xpath finds...
Read more

Selenium/Java-OOPs-Encapsulation

Image
We have started to learn OOPs concepts from last post, starting with Abstraction. In this post, we will go through the concept of Encapsulation.  Encapsulation: Basically, Encapsulation binds data(variables) and code together. It is a process of wrapping up the data in single unit. We declare our variables as private, so it can not be accessed outside the class. Hence, it is also called data hiding approach. However, if you wish to access the variables outside the class, we can use public setter and getter methods to access such private variables.  The first question arises here is, why to declare variables as private if anyway we can use it outside the class using setter and getter methods.. !! That's where the concept of Encapsulation flourishes..!! Here, we are declaring variables as private and hence one can not get the idea about the implementations of the class. User can only surmise that how the variable will be stored (It can be String, integer ...
Read more

Selenium: Waits

Image
In last post, we have seen how Xpath helps us to find dynamic elements which changes every time. Similarly, most of the front ends are developed with Ajax and JavaScript where different elements load at different time. In such cases, our driver need to wait till the element is loaded and visible otherwise it will throw ' elementNotVisibleException ' exception and eventually our automation script will fail. To avoid such situations we have one powerful option in selenium that is nothing but ' Wait '. [ source: www.deshannonspeaks.com ] In general, we have two types of wait in selenium. Implicit wait Explicit wait 1. Implicit Wait :  This idea is borrowed from Watir. Here, we are instructing our driver to wait for certain amount of time for element to get loaded before throwing an exception. Example : Consider our Facebook login scenario. Implicit wait syntax is highlighted in bold. It will wait for 10 seconds and if any element is not loaded i...
Read more

Selenium: BDD- The Disruptive Framework

As we learnt about different selenium automation framework in last post, now it is time to focus on one particular framework which will shape the future of selenium automation testing and that is nothing but Behavior Driven Development (BDD) framework !  BDD serves as a bridge between tech and non-tech people which includes but not limited to developers, testers, clients and business analysts. In BDD, we can write our automation tests in general English like language which can be understand by all the stake holders and eventually it paves the way for smoother functioning and more productive environment. With the coming of agile model, concepts such as BDD has found more meaning and usage. The important feature of BDD is that it includes all the stake holders. Features of BDD:  Collaboration between developer team, QA team, client and business analysts. It uses plain English like language 'Gherkin' to describe tests. It augments business value by thinking in term...
Read more

Selenium: Capturing the screenshot

Image
As an QA engineer, we all know that taking the screenshots is the main task we do during testing particular application. (It works as a 'Brahmastra' while fighting with developers and clients !!). Similarly, while running automation scripts it is necessary to take screenshots of important events and functionalities as it is imperative for bug analysis.  Selenium offers great advantage of taking automatic screenshots during the execution. We can convert our WebDriver instance to TakesScreenshot . Below we will see one example of taking the screenshots in our selenium automation script. [source: www.qaautomated.com ] Example:  Here, simply we will try to open Google, will take the screenshot of that screen and we will store it to our local machine. // importing the needed jar files import org.openqa.selenium.WebDriver; import org.openqa.selenium.chrome.ChromeDriver; import com.sun.jna.platform.FileUtils; //creating class ScreenShot @...
Read more

Selenium: Frameworks

Image
In previous posts, we learnt about all the selenium basics for automation script writing. Now, let's move forward with some advance selenium topics such as Framework .  Framework is nothing but set of some predefined protocols and guidelines that how the things will work when we are writing automation scripts. Framework is like 'Single Standard' which is every automation tester is obliged to follow. Basically, framework helps to separate our 'code' and 'data' which will help in achieving higher code readability, reusability and portability. With the help of frameworks, we can test our script with multiple set of data which paves way for very efficient functional testing.   The main advantage of using frameworks is project maintenance as we can easily manage all our automation scripts, test data and all other related stuffs. e.g. different testers work on different modules of the AUT(Application Under Test)  and with the help of frameworks, we can e...
Read more

Selenium/Java-Interface

Image
In last post, we learnt about Polymorphism in Java which was the last main OOPs concept. In this post, we will go through the concept of Interface and will see how it is extremely useful while writing codes. An Interface in Java is just like a class but it implicitly contains only Abstract and Public methods that has only signature but not method body where as class can contain public, private and protected methods.   Implements keyword is used in Interface just like extends keyword is used in class.  An Interface can be defined as a blue print of the class as when the class implements the Interface it needs to override all the methods defined in Interface. When the class does not implements all the methods defined in an Interface, we need to define that particular class as Abstract.  [Source: www.ashtpoint.com ] An Interface is used mainly for two reasons: We can achieve complete or 100% abstraction as all the methods defined in an Interface a...
Read more