Versions Compared

Old Version 27

changes.mady.by.user Isabel Moreira

Saved on

compared with

New Version 28

changes.mady.by.user Diamantino Campos

Saved on

Key

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

...

Table of Contents

Upgrading to Xray 3.2.0

...

From Xray 3.2.0, the amount of information indexed in JIRA Lucene framework has increased. In order to not increase the index time, Xray is now pre-calculating this data so when re-indexing there is less calculation.

When installing Xray 3.2.0 the first time, this implies that an upgrade task must run to pre-calculate the data from the past. This process may be long depending on the JIRA instance size. This action is a one time action and it will be running in the background. Xray will still be available and it is making actions to guarantee there is no inconsistent data but as this action can be heavy, we recommend to perform the upgrade at a low usage time.

...

After installing version 3.2.0 of Xray, a re-index operation of your Jira instance is required so that the data becomes available in the required format.


Downgrading from Xray 3.2.x

...

titleRe-indexing JIRA

...

Downgrading from Xray 3.2.x implies that you must reindex after. This is because from Xray 3.2.0, the content and format of what Xray indexes have changed.


Release highlights 


Panel
borderColor#F3F3F3
bgColor#FAFAFA
borderWidth1px
Section

Automated Steps Library and enhanced edition for Cucumber Tests/Pre-Conditions


Column
width60%

Automation requires a lot of maintenance effort. There's the need of doing refactoring at many different levels, including at the specification level. This is even more true if you're adopting BDD and Cucumber. As your projects grow, the number of Cucumber Scenarios/Backgrounds will also increase, as will also the amount of Cucumber steps used by them.

Since (Cucumber) steps can, and shall, be used across different test specifications, you may need to do some refactoring on your existing steps in order to avoid duplicates and as means to foster reusability.


Thus, the Automated Steps Library provides one central place to see and manage all the Cucumber steps used in the context of some given project, allowing you to classify/label steps and refactor them (update, merge). You can even quickly identify the entities using those steps.

Steps are added automatically to the Automated Steps Library upon the creation/edition of Tests or Pre-Conditions. As soon as they're in the library, they can be used afterwards for easing the creation/updating of Cucumber Tests/Pre-Conditions, using autocomplete and filtering steps based on labels.


You can now be much more proficient using the enhanced editor for Cucumber based Tests/Pre-Conditions, right inside Jira.


Learn more here.

Column
width40%





...