Automation
- 1. Selenium Framework • Selenium Framework is Built using Ruby and Selenium/Webdriver tool. • Framework is capable of executing using Ant command. • Framework provides the option to execute scripts at groups level by providing the tag names and priority. • Tags and priority are added to each scripts as properties.
- 2. Hudson Integration • The main point of integration between the Selenium framework and Hudson concerns the ability to configure and execute test runs via a Hudson job • The Ant Buildfile The Selenium Ant buildfile provides several targets that can be used to run Selenium tests, along with a set of overridable default properties to control the configuration of the test runs.
- 3. Hudson Job Configuration Select "New Job", then choose "Build a free-style software project". This job type consists of the following elements: 1. optional SCM, such as CVS or Subversion where your source code resides. 2. optional triggers to control when Hudson will perform builds. 3. Some sort of build script that performs the build (ant, maven, shell script, batch file, etc.) where the real work happens 4. optional steps to collect information out of the build, such as archiving the artifacts and/or recording javadoc and test results. 5. optional steps to notify other people/systems with the build result, such as sending e-mails, IMs, updating issue tracker, etc.
- 4. Hudson - Job Execution
- 5. Hudson - Result Analysis
- 6. iAnalysis - Vision iAnalyze URL :http://ianalyze.qa.linkedin.com/ 1. Time optimization and build health snap shot. 2. Need to Store Data, which helps to see the previous history of the script while analyzing the script . 3. Customized reports and graphs. 4. To overcome the communication lag by sharing the information among the QA teams.
- 7. iAnalyze- Advantages 1. To reduce the QA engineers effort while analyzing the script by providing previous history. 2. To have an centralized data sharing with other QA Engineers. 3. To reduce the effort of time for preparing the reports. 4. To make the Engineers to identify the issue and show the path with past history. 5. Association of bug to a script.