Page History

...

Gwen also separates declarative from imperative style Gherkin specifications. Declarative is done in standard .feature files that may include steps defined in while imperative speficationsspecifications (i.e. "meta-features") are managed in .meta files.

Gwen Web Automation (gwen-web) is an engine that extends Gwen and adds capabilities for easy web testing using Selenium under the hood, by providing a DSL that allows users to interact with the browser without having to write code.

...

We will use sample code from gwen-web repository, using some instructions available online.

Remember that we need to manage:

• features (declarative specifications, usually stored in .feature files)
• meta-features (imperative specifications, usually stored in .meta files)

Besides that, you need The first thing to decide is which workflow we'll use: do we want to use Xray/Jira as the master for writing the declarative specification or do we want to manage those in Git?

Using Jira and Xray as master

This section The tutorial assumes using Xray as master; however, you can edit your .feature and .meta files outside of Jira (eventually storing them in you VCS using Git, for example) - more on that on the final section.

...

, i.e. the place that you'll be using to edit the specifications (e.g. the scenarios that are part of .feature files).

The first step is to create a Cucumber Test, of Cucumber Type "Scenario", in Jira. The specification would be exactly the same as the one provided in the original repository.

...

Using Git or other VCS as master

You can edit your .feature and .meta files outside of Jira (eventually storing them in your VCS using Git, for example).

In any case, you'll need to synchronize your .feature files to Jira so that you can have visibility of them and report results against them.

...

Given I have Google in my browser
When I do a search for "Gwen automation"
Then the first result should open a Gwen page

...