Skip to main content

About Selenium


Let's start with a basic information about Selenium.

Selenium:

It is basically a tool or framework that is used to automate web browsers. By using selenium you can automate a lots of web browsers like Firefox, IE, Chrome etc. 

It is possibly most widely used open source solution. Selenium is basically a set of different tools with different purpose and role. E.g.
  • Selenium IDE
  • Selenium 1 (Selenium RC)
  • Selenium 2 ( Selenium Webdriver)
  • Selenium-Grid
Selenium webdriver is the one which we will be using during this course. It supports following browsers:
  • Google Chrome
  • Internet Explorer
  • Firefox
  • Safari
  • Opera
  • HtmlUnit
  • phantomjs
  • Android
  • iOS
So, it is the one that allows you to automate these web browsers. If we talk little bit technically, then it is basically an API for web browsers. Using this you can program web browsers in a way that you want them to do.

If you want to learn more about selenium then you can go through this link.

Architecture for Selenium WebDriver:




You don't actually have to bother about what exactly this architecture depicts, but you should at least have a general idea of how it works.

As from above diagram you can see that selenium web driver API lies between browser drivers and language bindings. 

Each browser driver knows how to interact with respective browser elements. Selenium web driver sends commands to these driver servers which in turn executes the commands and sends back the result. 

Language bindings are just the implementations in various languages that can be used for automation. 

So, we have a common API with common set of commands and we have various bindings for different languages. These bindings communicate with the common API i.e. web driver API.


In my next post I will be explaining you how to setup environment for developing automation framework in selenium, so keep in touch.



Thanks for reading this post. See you in next post. Cya!








Comments

Popular posts from this blog

Logging in Selenium - To File

In my previous post I explained you how you can configure log4net in your project to do logging to console with example. Now, in this post I will be explaining how we can configure log4net to log to file instead of console. As we already have working logs to console from our TestFramework so logging to file doesn't take much efforts. You just need to follow below steps and you are done. Configuring log4net to log to file Step 1 : Add an " app.config " file in your UITests project with content as shown below: Step 2:   Change configurator in Configure method of Log class That's it. Now, when you will run the test it will log to console as well as file named " Test.log ". This file can be found at \TestFramework\UITests\bin\Debug location in you project folder. As you saw, we just added app.config file and then changed the configurator in order to log to file. Earlier we used "BasicConfigurator.Configure()" which writes logs to cons...

Logging in Selenium

Any application is incomplete until it's activities are traceable. Here comes the use of logging. By logging important actions you can later on track anything you want especially when there are some error situations. It becomes easy to debug the issues if logs are generated properly. Similarly, it is very important that our automation framework generates logs so that whenever any test fails, we can track the issue by tracing it's logs. In this post, I will be explaining you how we can log using log4net in selenium. Before using methods of this library we need to configure this to our application. Let's do this first then. Configuring log4net in selenium: First of all you need to download this library so that this can be used. You can read about log4net and then download it from this link and save the dll file after extracting it to folder that is under your project folder. After downloading this library you need to add references of this in you project. To do ...

SELENIUM: Some Useful Facts

Before we start designing a framework, there are few facts that we should always remember. It is not important what you have designed, it is more important that how good your product is. Also, this kind of analysis should always be done in the beginning so that you don't have to devote extra time and efforts for it later. It is always good to fix something in beginning than worrying about it later when it has become a big issue and become difficult to locate the issue. It's not like that we won't be able to fix it, we will definitely fix it but with more cost and efforts. Let's go through few of these facts. Layers in Framework You should always keep in mind the layers that should be there in the framework you are designing. Layers to be created generally varies application to application that you are creating but most of the frameworks contains below layers often. In above picture, there is workflow layer at the top. Workflows can be think of as somet...