Versions Compared

Old Version 4

changes.mady.by.user Sergio Freire

Saved on

compared with

New Version 5

changes.mady.by.user Unknown User (tdda)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Gherkin is mainly used in BDD (behaviour-driven development) context. However, please note that Gherkin and BDD are two different thinksthings: you may use Gherkin to describe your test scenarios and still not following follow BDD.


BDD starts by having a clear understanding of the business value, or the ultimate benefit , of a user story, which is done by describing it properly (e.g. "As a ..., I want to ..., So that [benefit]").

Having it this understanding in mind will help depicting to depict "behaviours" that the system must address; these are the actual acceptance criteria, which are described in scenarios using an a “ubiquitous language”, as Dan North states. Gherkin can be used to provide the foundations of this language.

Key to BDD is having a shared/common understanding of the purpose of the feature: what is it supposed to do and why. This can be done collaboratively by the so-called "three amigos" (i.e. people from the business, development/coding and testing roles), which in the end need to agree on what composes a "feature" (i.e. the story itself along with the respective acceptance criteria as scenarios).

...

Xray provides the tooling to create and manage the specification inside Jira and to import/export it; however. However, how the implementation is managed is outside of Xray's scope.

...

Supported features

Xray has a comprehensive support for Gherkin. First, it supports the creation of Scenarios and Scenario Outlines as Test cases, using the one of the possible values for the "Test Type" field (e.g. Gherkin, Cucumber).

...

The next sections detail in more depth all the features support supported by Xray.

Main features

...