how to install selenium ide plugin on jenkins

In 2009, after a meeting between the developers at the Google Test Automation Conference, it was decided to merge the two projects and call the new project Selenium WebDriver, or Selenium 2.0. At the same time, Simon Stewart at ThoughtWorks developed a superior browser automation tool called WebDriver. Together with others like Jennifer Bevan, he continued with the development and stabilization of Selenium RC. He came up with this idea to further increase the speed in creating test cases. He created Selenium as a Firefox extension that can automate the browser through a record-and-playback feature.

In 2006, Selenium IDE was donated to Selenium Project by Shinya Kasatani of Japan. In the same meeting, the steering of Selenium as a project would continue as a committee, with Huggins and Hammant being the ThoughtWorks representatives.

In 2005 Dan Fabulich and Nelson Sproul (with help from Pat Lightbody) made an offer to accept a series of patches that would transform Selenium-RC into what it became best known for. Huggins was later joined by other programmers and testers at ThoughtWorks, before Paul Hammant joined the team and steered the development of the second mode of operation that would later become “Selenium Remote Control” (RC). Selenium was originally developed by Jason Huggins in 2004 as an internal tool at ThoughtWorks.

How to install selenium ide plugin on jenkins