Gherkin is a language like plain English used to specify features of a system.
Gherkin serves two purposes — documentation and automated tests.
Gherking allows creating tests in collboration with non-technical stakeholders in product (product owners, business team, manual testers).
In Gherkin, each line that isn't blank has to start with a Gherkin keyword, followed by any text you like. The main keywords are:
FeatureScenarioGiven,When,Then,And,But(Steps)BackgroundScenario OutlineExamples
There are a few extra keywords as well:
"""(Doc Strings)|(Data Tables)@(Tags)#(Comments)
Cucumber executes the Gherkin files.
It maps each line from the gherkin file to a step written in ruby. This allows us to automate the specification written in gherking language using ruby (or any other language).
Refer : https://en.wikipedia.org/wiki/Selenium_(software)#Selenium_WebDriver
Selenium WebDriver accepts commands (via a Client API) and sends them to a browser. This is implemented through a browser-specific browser driver, which sends commands to a browser, and retrieves results. Most browser drivers actually launch and access a browser application (such as Firefox, Chrome, Internet Explorer, or Microsoft Edge)
Refer: http://watir.com/
Watir is a pragrammer friendly ruby interface to Selenium Webdriver API. It provides more readable and concise code for interacting with elements on a webpage, while using Webdriver beneath the surface.
- Install chrome webdriver from https://sites.google.com/a/chromium.org/chromedriver/getting-started
- Git clone the repository
- Open project directory
- Install gems
- Run with rake command
Load test data with rake command db:play, create data using UI or rails console, run db:record and checkin.