Our customers have been loving the ability to write and execute (simple English) Cucumber Automated Testing Scripts for a while now. Cucumber has been one of the primary frameworks for BDD and its benefits are clearly proven by the fact that many new automation technologies like Calabash are actively using it.

At 3Qi, we’ve actively used and promoted Cucumber for several years now, and in addition to its many benefits that have been promoted by the community, the big one our customers have realized is the fact that all stakeholders (Business, Dev & QA) can understand, quantify and agree upon test coverage right from the onset. This is a big deal in the enterprise since, historically, some of this has been a “black box” (no pun intended!).

As part of Awetest, we have defined a core set of Cucumber steps that account for the bulk of the interactions in most web applications. Our Cucumber steps use the Watir WebDriver API under the covers to drive the browsers but this complexity has been abstracted out so that users can build simple automated testing scripts without having to go in and write custom libraries in the initial phases of their automation buildout.

Below is a cheat sheet, a listing of all the predefined Cucumber steps that ship with Awetest.  We are constantly adding and updating this library and you can always find more details at http://awetest.zendesk.com

Opening a browser:
These are standard commands for launching a browser. You can specify a browser or you can simply say “new browser” which will launch the browser you selected at run time in Awetest.

Defining Library:
Awetest supports both Classic Watir and Watir WebDriver and you can choose the library you want to use directly in the script.

This is standard navigation to a specific URL. You can also specify environments in Awetest directly which will be used by the scripts at Run time.

Clicking on an image/text:

Interacting with button/radio/check box:

Inputting data into text field:

Selecting from the target list:

Checking the value in a text box:

Text validation:

Filling in a text box:

Using Binding.pry to debug:

Implicit & Explicit Waits:

Interacting with browser alert:

Closing the browser:

Special Cases:

Cucumber continues to be a big draw for enterprise customers. In addition to the natural language (simple english) syntax, Awetest customers love the fact that they can use the same steps and feature files (Cucumber scripts) to execute their cross browser and mobile tests.