Automation Trivia

Hi followers,  Thanks for the great support and it make me more enthusiastic to post more stuffs related to Selenium. In this post we will see how to integrate Selenium Scripts with Jenkins.  First we will look what is Jenkins, why we need that and what is the benefit we are going to achieve because of Selenium integration Jenkins is an open source continuous integration tool written in Java. Jenkins provides continuous integration services for software development. It is a server-based system running in a servlet container such as Apache Tomcat. It supports SCM tools including CVS, Subversion, Git, Mercurial, Perforce and Clearcase, and can execute Apache Ant and Apache Maven based projects as well as arbitrary shell scripts and Windows batch commands. Builds can be started by various means, including being triggered by commit in a version control system, scheduling via a cron-like mechanism, building when other builds have completed, and by requesting a specific build

Selenium is a browser automation tool, commonly used for writing end-to-end tests of web applications. A browser automation tool does exactly what you would expect: automate the control of a browser so that repetitive tasks can be automated. It sounds like a simple problem to solve, but as we will see, a lot has to happen behind the scenes to make it work. At a very high level, Selenium is a set of different software tools each with a different approach to supporting test automation. They are, > Selenium IDE > Selenium Grid > Selenium WebDriver aka Selenium2 History of Selenium Jason Huggins started the Selenium project in 2004 while working at ThoughtWorks on their in-house Time and Expenses (T&E) system, which has extensive use of Javascript. Fortunately, all the browsers being tested supported Javascript.  Inspired by work being done on FIT, a table-based syntax was placed over the raw Javascript and this allowed tests to be written by people with limited