Page History
The Automated Steps Library is a project-level steps library organization for Cucumber Tests/PreconditionsPre-Conditions, containing all the Gherkin steps referred by all those Tests/Preconditions Pre-Conditions belonging to that project.
...
The library is automatically populated with all the steps upon the creation/update of Cucumber Tests/PreconditionsPre-Conditions.
Gherkin reserved keywords (e.g. Given, When, Then, And) are not stored in the library.
...
- B1: step content (i.e. Gherkin sentence without the Gherkin reserved keywords)
- B2: information about the Test(s)/PreconditionPre-Condition(s) using the selected step
- B3: labels assigned to the step
...
Info | |||||
---|---|---|---|---|---|
| |||||
Upon a steps merge operation, all Tests and Preconditions Pre-Conditions using it are updated accordingly. Only non-readonly Tests/Preconditions Pre-Conditions that the user is allowed to edit are updated; the other ones will remain as-is, leading to the simultaneous existence of original steps along with the merged one in the library, in this case. A merge operation may require some manual reviewing on the destination affected Tests/PreconditionsPre-Conditions. Example: two steps are merged to one having the content: "Given I have a turned on calculator"
As you can see from this example, in which the original Test/Precondition Pre-Condition contains the original steps, the merge operation does not remove duplicated steps in the destination Cucumber Scenario/Background. Thus, a manual process should be done on the affected issues in order to review the specification and remove the steps where desired. |
...
Step 3: Edit the merged step content on the right side; on the left side you can see the temporary merged step until you save it.
Step 4: Click on Save.
Find Tests and
...
Pre-Conditions using a step
To find all the Tests or Preconditions Pre-Conditions using a given step:
Step 1: Click on the step.
...
The step content can be updated (i.e. renaming the step) directly in the Automated Steps Library for easy refactoring; all updatable Tests/Preconditions Pre-Conditions will be updated accordingly.
Only non-readonly Tests/Preconditions Pre-Conditions that the user is allowed to edit are updated; the other ones will remain as-is, leading to the simultaneous existence of original step along with the updated one in the library, in this case.
...
Info | ||
---|---|---|
| ||
It is also possibile to indirectly update steps during the edition of Cucumber Tests/PreconditionsPre-Conditions; however, this inhibits refactoring. Whenever editing Cucumber Tests/PreconditionsPre-Conditions, if the changed steps aren't being used elsewhere, then the existing steps will be updated accordingly; otherwise, new steps will be created. In other words, the library will contain all the steps, including the new/changed ones along with the "original" ones that being used in other issues. Thus, some care should be taken whenever editing Cucumber Tests/Preconditions Pre-Conditions in order to avoid proliferation of similar steps. |
...
A setting availabe in Xray Global Preferences Miscellaneous allows the administrator to enable/disable the library.
...
Whenever enabled, there's an additional performance overhead on the creation/update of Cucumber Tests/Preconditions Pre-Conditions and upon the refactoring of existing steps within the Automated Steps Library UI.
...
Info | ||
---|---|---|
| ||
if you disable the Automated Steps Library, all new steps that you added meanwhile or, in general, any changes that you have made to your existing Cucumber Tests/Preconditions Pre-Conditions afterwards will not be synchronized to the library. This means that the Automated Steps Library may be out-of-synch. Synchronizing your existing steps with the library can be done with the Integrity Checker. |
...