Selenium For Beginner's

Posted by Infocampus HR on July 9th, 2018

Selenium For Beginner's

Introduction to Selenium

What is Selenium?

Selenium is a free (open source) computerized testing suite for web applications crosswise over various programs and stages. It is very like HP Quick Test Pro (QTP now UFT) just that Selenium centers around mechanizing online applications. Testing done utilizing Selenium instrument is typically alluded as Selenium Testing.

Selenium isn't only a solitary instrument however a suite of software's, each taking into account diverse testing needs of an association. It has four parts.

•           Selenium Integrated Development Environment (IDE)

•           Selenium Remote Control (RC)

•           WebDriver

•           Selenium Grid

Right now, Selenium RC and WebDriver are converged into a solitary structure to shape Selenium 2. Selenium 1, incidentally, alludes to Selenium RC.

Who created Selenium?

Since Selenium is an accumulation of various apparatuses, it had distinctive designers too. The following are the key people who influenced striking commitments to the Selenium To extend

Prologue to Selenium

Basically, Selenium was made by Jason Huggins in 2004. A specialist at Thought Works, he was taking a shot at a web application that required successive testing. Having understood that the redundant manual testing of their application was winding up increasingly wasteful, he made a JavaScript program that would consequently control the program's activities. He named this program as the "JavaScriptTestRunner."

Seeing potential in this plan to help mechanize other web applications, he made JavaScriptRunner open-source which was later re-named as Selenium Core.

Same Origin approach precludes JavaScript code from getting to components from an area that is not the same as where it was propelled. Illustration, the HTML code in www.google.com utilizes a JavaScript program "randomScript.js". A similar starting point approach will just enable randomScript.js to get to pages inside google.com, for example, google.com/mail, google.com/login, or google.com/information exchange. Be that as it may, it can't get to pages from various destinations, for example, yahoo.com/seek since they have a place with various spaces.

This is the motivation behind why before Selenium RC, analyzers expected to introduce neighborhood duplicates of both Selenium Core (a JavaScript program) and the web server containing the web application being tried so they would have a place with a similar space

Birth of Selenium Remote Control (Selenium RC)

Tragically; analyzers utilizing Selenium Core needed to  Best Selenium Institute in Marathahalli Bangalore introduce the entire application under test and the web server all alone neighborhood PCs due to the limitations forced by a similar source approach. So another ThoughtWork's architect, Paul Hammant, chose to make a server that will go about as a HTTP intermediary to "trap" the program into trusting that Selenium Core and the web application being tried originated from a similar space. This framework ended up known as the Selenium Remote Control or Selenium 1.

Birth of Selenium Grid

Selenium Grid was produced by Patrick Lightbody to address the need of limiting test execution times however much as could be expected. He at first called the framework "Facilitated QA." It was equipped for catching program screen captures amid noteworthy stages, and furthermore of conveying Selenium charges to various machines at the same time.

Birth of Selenium IDE

Shinya Kasatani of Japan made Selenium IDE, a Firefox expansion that can mechanize the program through a record-and-playback highlight. He thought of this plan to additionally expand the speed in making experiments. He gave Selenium IDE to the Selenium Project in 2006.

Birth of WebDriver

Simon Stewart made WebDriver around 2006 when programs and web applications were ending up more intense and more prohibitive with JavaScript programs like Selenium Core. It was the primary cross-stage testing structure that could control the program from the OS level.

Birth of Selenium 2

In 2008, the entire Selenium Team chose to combine WebDriver Selenium Training in Marathahalli Bangalore and Selenium RC to shape an all the more ground-breaking instrument called Selenium 2, with WebDriver being the center. At present, Selenium RC is as yet being created yet just in support mode. The majority of the Selenium Project's endeavors are currently centered around Selenium 2.

Things being what they are, Why the Name Selenium?

It originated from a joke which Jason broke one an opportunity to his group. Another mechanized testing structure was famous amid Selenium's advancement, and it was by the organization called Mercury Interactive (yes, the organization who initially made QTP before it was procured by HP). Since Selenium is a notable cure for Mercury harming, Jason recommended that name. His colleagues took it, thus that is the means by which we got the opportunity to ring this structure to the present.

Brief Introduction Selenium IDE

Selenium Integrated Development Environment (IDE) is the most straightforward structure in the Selenium suite and is the least demanding one to learn. It is a Firefox module that you can introduce as effectively as you can with different modules. Nonetheless, due to its effortlessness, Selenium IDE should just be utilized as a prototyping apparatus. On the off chance that you need to make further developed experiments, you should utilize either Selenium RC or WebDriver.

Brief Introduction Selenium Remote Control (Selenium RC)

Selenium RC was the leader testing system of the entire Selenium venture for quite a while. This is the principal mechanized web testing device that enabled clients to utilize a programming dialect they lean toward. As of variant 2.25.0, RC can bolster the accompanying programming dialects:

Java

C#

PHP

Python

Perl

Ruby

Brief Introduction WebDriver

The WebDriver ends up being superior to both Selenium IDE and Selenium RC in numerous perspectives. It executes a more present day and stable approach in computerizing the program's activities. WebDriver, not at all like Selenium RC, does not depend on JavaScript for Automation. It controls the program by straightforwardly speaking with it.

The upheld dialects are the same as those in Selenium RC.

Java

C#

PHP

Python

Perl

Ruby

Selenium Grid

Selenium Grid is an instrument utilized together with Selenium RC to run parallel tests crosswise over various machines and distinctive programs all in the meantime. Parallel execution implies running numerous tests without a moment's delay.