|This article needs additional citations for verification. (October 2012) (Learn how and when to remove this template message)|
|Developer(s)||Bret Pettichord, Charley Baker, Angrez Singh, Jari Bakken, Jarmo Pertman, Hugh McGowan, Andreas Tolf Tolfsen, Paul Rogers, Dave Hoover, Sai Venkatakrishnan, Tom Copeland, Alex Rodionov, Titus Fortner|
|Stable release||5.0 / October 5, 2013|
|Preview release||6.0.0.beta3 / August 7, 2016|
|Type||Software testing framework for web applications|
Watir (Web Application Testing in Ruby, pronounced water), is an open-source family of Ruby libraries for automating web browsers. It drives Internet Explorer, Firefox, Chrome, Opera and Safari, and is available as a RubyGems gem. Watir was primarily developed by Bret Pettichord and Paul Rogers.
Watir project consists of several smaller projects. The most important ones are watir-classic, watir-webdriver and watirspec.
Watir-classic makes use of the fact that Ruby has built in Object Linking and Embedding (OLE) capabilities. As such it is possible to drive Internet Explorer programmatically. Watir-classic operates differently than HTTP based test tools, which operate by simulating a browser. Instead Watir-classic directly drives the browser through the OLE protocol, which is implemented over the Component Object Model (COM) architecture.
The COM permits interprocess communication (such as between Ruby and Internet Explorer) and dynamic object creation and manipulation (which is what the Ruby program does to the Internet Explorer). Microsoft calls this OLE automation, and calls the manipulating program an automation controller. Technically, the Internet Explorer process is the server and serves the automation objects, exposing their methods; while the Ruby program then becomes the client which manipulates the automation objects.
Watir-webdriver is a modern version of the Watir API based on Selenium. Selenium 2.0 (selenium-webdriver) aims to be the reference implementation of the WebDriver specification. In Ruby, Jari Bakken has implemented the Watir API as a wrapper around the Selenium 2.0 API. Not only is Watir-webdriver derived from Selenium 2.0, it is also built from the HTML specification, so Watir-webdriver should always be compatible with existing W3C specifications.
Watirspec is executable specification of the Watir API, like RubySpec is for Ruby.
- Celerity is a JRuby wrapper around HtmlUnit, aimed at being API compatible with Watir.
- Symbiont proxies Watir-WebDriver to page objects along with a minimalist API.
- WatiN (pronounced What-in) stands for Web Application Testing In .NET. It is inspired by Watir and implemented in .NET Framework.
- Watij (pronounced wattage) stands for Web Application Testing in Java. It is inspired by Watir and implemented in Java.
- Win32::Watir is inspired by Watir and implemented in Perl.
- win-control is inspired by Watir and implemented in Gambit (Scheme implementation).
- Selenium (software) is a browser automation framework and ecosystem.
- Watir for Rails is a library for using Watir with Rails.
- Pincers is a jQuery inspired Ruby DSL on top of webdriver.
- Capybara is an acceptance test framework for web applications.
- "Watir home page". Watir web site. Retrieved 11 October 2012.
- "A new member in the Watir-family". Opera Software web site. Opera Software. Retrieved 11 October 2012.
- "Watir to WebDriver: Unit Test Frameworks". Facebook Engineering's Notes. Facebook. Retrieved 11 October 2012.
- Crispin, Gregory (2008). Agile Testing: A Practical Guide for Testers and Agile Teams. Addison-Wesley. p. 172. ISBN 9780321534460.
- Marick, Brian (2007). Everyday Scripting with Ruby: For Teams, Testers, and You. Pragmatic Bookshelf. p. 2. ISBN 9780977616619.
- "Creating automated test scripts with Ruby and WATIR". ThoughtWorks web site. ThoughtWorks. Retrieved 11 October 2012.