{"id":757,"date":"2013-01-02T07:29:32","date_gmt":"2013-01-02T07:29:32","guid":{"rendered":"http:\/\/vskills.in\/certification\/tutorial\/?p=757"},"modified":"2024-04-12T14:12:59","modified_gmt":"2024-04-12T08:42:59","slug":"selenium-evolution","status":"publish","type":"page","link":"https:\/\/www.vskills.in\/certification\/tutorial\/selenium-evolution\/","title":{"rendered":"Selenium Evolution | Selenium Webdriver"},"content":{"rendered":"\n
\"Selenium<\/a><\/figure><\/div>\n\n\n

Selenium Evolution | Selenium Webdriver<\/strong><\/h2>\n

\u00a0<\/p>\n

It is important to learn about Selenium Evolution | Selenium Webdriver. The story of selenium evolution<\/strong> started in the year 2004 in Chicago at ThoughtWorks. At that time Jason Huggins was building the Core mode as “JavaScriptTestRunner”<\/strong> in order to test of an internal Time and Expenses application. The focus of to ThoughtWork’s style was automatic testing of any applications, which gave the Agile leanings of this consultancy. Jason Huggins was helped by Paul Gross and Jie Tina Wang in the Selenium Evolution. Jason showed the test tool to his colleagues. Every one was very positive and excited about it. The immediate and intuitive visual feedback of the selenium webdrivers, as well as the potential to grow as a reusable testing framework for other web applications.<\/p>\n

Then after 2004 fellow ThoughtWorker Paul Hammant watched the demo, and started discussions about the open sourcing of Selenium. They defined a ‘driven’ mode of Selenium where one has to use Selenium over the wire from a language of choice, that would get around the ‘same origin policy’. The original server piece was written in Java by Paul. Thereafter Aslak and Obie Fernandez ported that the client driver to Ruby, which led to setting of the the foundation for Selenium webdrivers<\/strong> in many more languages.<\/p>\n

ThoughtWorkers picked up Selenium for commercial projects in various offices around the world, and thereby provideed feedback from the lessons learned on these projects. Thereafter Mike Williams, Darrell Deboer, and Darren Cotterill helped with the increasing the capabilities and the robustness of Selenium Webdrivers.<\/p>\n

Simon Stewart at ThoughtWorks worked a various web testing tool called WebDriver.<\/strong> These selenium webdrivers<\/strong> did not rely on JavaScript, instead each browser was assigned to a client which was was coded from scratch. This also had a ‘higher level’ API than Selenium-RC<\/strong> which had huge scope. Then Simon presented the tool at GTAC, on compatibility with Selenium-RC, which gave rise to the obvious conclusion that the two projects should merge. Simon, worked at Google from 2007 to 2012, and is now at Facebook. He now spend some of his time making it a reality.<\/p>\n

Suggested video<\/span><\/p>\n