Page History

...

On the left side of UI steps can be searched and filtered by labels, while on the right side the step content can be edited and saved.

Steps are case insensitive and their content is trimmed (i.e. spaces removed at the start/end).

The Automated Steps Library provides the means to:

• refactor steps, by easily renaming them (i.e. changing their specification)
• refactor steps, by merging similar steps and avoiding duplicated specifications & associated code
• see which Tests/Preconditions are using a particular step
• label steps, so they can be categorized, to ease their management and the step autocompletion during Test/Precondition edition

Steps

Steps, from the current Automated Steps Library perspective, correspond to Gherkin sentences used by Cucumber Tests/Preconditions (i.e. Cucumber Scenario, Scenario Outline, Background).

Steps are case insensitive and their content is trimmed (i.e. spaces removed at the start/end).

Gherkin reserved keywords (e.g. Given, When, Then, And) are not stored in the library, so these two following steps are equally stored as "I have a calculator":

Given I have a calculator

And I have a calculator

Steps can be updated/refactored in the Automated Steps Library; they can also be implicitly updated or created whenever editing or creating a Cucumber Test/Precondition.

However, they cannot be created from within the Automated Steps Library UI, in order to avoid dummy/unused steps. In other words, if a step appears in the Automated Steps Library then most probably it is been used by some entity. Exceptions may arise though, specially if the library is disabled somewhere in time or if for some reason Xray was unable to process an update/creation Jira event.

Integrity Checker may be used to force a per-project synchronization of steps, in case you find orphaned or missing steps in the library.