Selenium

Views:
 
Category: Entertainment
     
 

Presentation Description

No description available.

Comments

Presentation Transcript

Selenium:

Selenium

Agenda:

Agenda Introduction to Selenium Father of Selenium Same Origin Policy Birth of Selenium Remote Control(RC) Birth of Selenium Grid Birth of Selenium IDE Birth of Web Driver Birth of Selenium 2 Conclusion

Introduction to Selenium:

Introduction to Selenium Selenium is a free (open source) automated testing suite for web applications across different browsers and platforms. It is quite similar to HP Quick Test Pro (QTP now UFT) only that Selenium focuses on automating web-based applications. Testing done using Selenium tool is usually referred as Selenium Testing.

:

Selenium is not just a single tool but a suite of software's , each catering to different testing needs of an organization.  It has four components. Selenium Integrated Development Environment (IDE) Selenium Remote Control (RC) WebDriver Selenium Grid

Four components:

Four components

Father of Selenium:

Father of Selenium Primarily, Selenium was  created by Jason Huggins in 2004 . An engineer at ThoughtWorks, he was working on a web application that required frequent testing. Having realized that the repetitious  Manual Testing of their application was becoming more and more inefficient, he created a  JavaScript program that would automatically control the browser's actions. He named this program as the " JavaScriptTestRunner ." Seeing potential in this idea to help automate other web applications, he made JavaScript Runner open-source which was later re-named as  Selenium Core .

Origin policy issue:

Origin policy issue Same Origin policy prohibits JavaScript code from accessing elements from a domain that is different from where it was launched . Example, the HTML code in www.google.com uses a JavaScript program "randomScript.js". The same origin policy will only allow randomScript.js to access pages within google.com such as google.com/mail, google.com/login, or google.com/signup. However, it cannot access pages from different sites such as yahoo.com/search or guru99.com because they belong to different domains.

:


Birth of Selenium Remote Control:

Birth of Selenium Remote Control Unfortunately; testers using Selenium Core had to install the whole application under test and the web server on their own local computers because of the restrictions imposed by the  same origin policy .   So another ThoughtWork's engineer,  Paul Hammant , decided to create a server that will act as an HTTP proxy to "trick" the browser into believing that Selenium Core and the web application being tested come from the same domain. This system became known as the  Selenium Remote Control  or  Selenium 1 .

Birth of Selenium Grid:

Birth of Selenium Grid Selenium Grid was developed by  Patrick Lightbody  to address the need of minimizing test execution times as much as possible. He initially called the system " Hosted QA ." It was capable of capturing browser screenshots during significant stages, and also of  sending out Selenium commands to different machines simultaneously.

Birth of Selenium IDE:

Birth of Selenium IDE Shinya Kasatani   of Japan created  Selenium IDE , a Firefox extension that can automate the browser through a record-and-playback feature. He came up with this idea to further increase the speed in creating test cases. He donated Selenium IDE to the 

Birth of Selenium WebDriver:

Birth of Selenium WebDriver Simon Stewart  created WebDriver circa  2006  when browsers and web applications were becoming more powerful and more restrictive with JavaScript programs like Selenium Core.  It was the first cross-platform testing framework that could control the browser from the OS level.  

Birth of Selenium2:

Birth of Selenium2 In  2008 , the whole Selenium Team decided to merge Web Driver and Selenium RC to form a more powerful tool called  Selenium 2 , with  Web Driver being the core . Currently , Selenium RC is still being developed but only in maintenance mode. Most of the Selenium Project's efforts are now focused on Selenium 2.

Conclusion:

Conclusion Although selenium is highly toxic in many of its chemical forms, a number off actors suggest that it probably is not a significant pollution problem. The bulk of the industrial uses of selenium are such that only small amounts of the element are injected into the ecosphere . Un- doubtedly , the paucity of data on the selenium content of various environmental samples is partly due to the difficulty of performing selenium analyses .

Thank you :

Thank you

authorStream Live Help