Evolution of Selenium

Evolution of Selenium - Part 1

  1. Selenium Webdriver
  2. Selenium Record and playback IDE
  3. Selenium GRID

Why Selenium:

1. Its open-source and highly matured tool for web testing
2. Open source tool3. Selenium have huge user base with wider support4. User can choose different binding languages depends on need5. As it is language independent, it robust and easy to access Database or APIs for deep verification

Different Types of Selenium :

Selenium Webdriver 




If you are beginning with desktop website or mobile website test automation, then you sghould use WebDriver APIs. WebDriver uses browser automation APIs provided by browser vendors to control browser and run tests. This is as if a real user is operating the browser. Since WebDriver does not require its API to be compiled with application code, it is not intrusive. Hence, you are testing the same application which you push live.

Selenium IDE




IDE (Integrated Development Environment) is the tool you use to develop your Selenium test cases. It’s an easy-to-use Chrome and Firefox extension and is generally the most efficient way to develop test cases. It records the users’ actions in the browser for you, using existing Selenium commands, with parameters defined by the context of that element. This is not only a time-saver but also an excellent way of learning Selenium script syntax. The Con's of this is, this can be used with only simple websites. 


Selenium Grid



Selenium Grid allows you to run test cases in different machines across different platforms. The control of triggering the test cases is on the local end, and when the test cases are triggered, they are automatically executed by the remote end.

After the development of the WebDriver tests, you may face the need of running your tests on multiple browser and operating system combinations. This is where Grid comes into the picture.

Who uses Selenium


Many of the most important companies in the world have adopted Selenium for their browser-based testing, often replacing years-long efforts involving other proprietary tools. As it has grown in popularity, so have its requirements and challenges multiplied.

As the web becomes more complicated and new technologies are added to websites, it’s the mission of this project to keep up with them where possible. Being an open source project, this support is provided through the generous donation of time from many volunteers, every one of which has a “day job”.

Another mission of the project is to encourage more volunteers to partake in this effort, and build a strong community so that the project can continue to keep up with emerging technologies and remain a dominant platform for functional test automation.

History of Selenium


When Selenium 1 was released in 2004, it was out of the necessity to reduce time spent manually verifying consistent behaviour in the front-end of a web application. It made use of what tools were available at the time and relied heavily on the injection of JavaScript to the web page under test to emulate a user’s interaction.

Whilst JavaScript is a good tool to let you introspect the properties of the DOM and to do certain client-side observations that you would otherwise not be able to do, it falls short on the ability to naturally replicate a user’s interactions as if the mouse and keyboard are being used.

--Will be continued in next blog

Comments

Popular posts from this blog

How to inspect disappearing element in a browser:

Implicit vs Explicit vs Fluent And Sleep in Selenium

Selenium Page Object Generator Chrome Extension