Versions Compared

Old Version 1

changes.mady.by.user Sergio Freire

Saved on

compared with

New Version 2

changes.mady.by.user Sergio Freire

Saved on

Key

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

...

  1.  Don't add many custom fields to Tests as it will add some additional overhead to Jira.

  2.  Promote reusability and avoid cloning Test cases, if they’re the same. A Test can be reused multiple times and can be used to cover more than one requirement (if really needed), no matter in which project it is located.

  3.  We also recommend up to 5 linked Tests per each requirement; ideally a Test should be focused on the validation of one requirement.

    • This recommendation helps improve performance both on the TestRun Status and Requirement Status calculations and also when loading the issue screens.

Pre-Conditions

  1. Image Modified Although the impact is neglectable, try to use Pre-Conditions as means to have manageable end reusable initial conditions that you can link to multiple Tests. That will avoid creating additional steps in all those test cases.

Test Sets

  1.  Although there isn’t an hard limit, we recommend having no more than 2000 Tests in a given Test Set mostly to ease their management. This limit may be easily superseded depending on Jira instance deployment configuration.

...

  1.  Creating a Test Plan from within some Test Repository folder that has many Tests and sub-folders can take some time, if you choose to replicate the folder structure into the destination Test Plan Board. However, this is temporary.
  2.  Avoid many folders shown at the same time as it will impact browser performance at some time. You can do this by limiting of direct child folders you create at a given parent folder and by using the "Expand all" moderately. The amount of folders you have does not affect by itself your Jira backend performance though.

Test Executions

  1. Reuse  Reuse existing Test Executions
  2. Cleanup Cleanup

    1. If your organization performs a high number of Test Executions (consequently creating also a high number of Test Runs) we recommend deleting old Test Executions issues from time to time (e.g.1 year).

      This recommendation is mostly for organizations that import lots of automated executions daily using the Xray REST API.

      The clean process must be scheduled for a period when there is a low Jira usage because when Test Executions are deleted, Xray will re-calculate TestRun Status and Requirement Status. This might slow down the Jira instance depending on the amount of issues affected.

  3.  Although there isn’t an hard limit, we recommend having no more than 2000 Tests in a given Test Execution mostly to ease their management. This limit may be easily superseded depending on Jira instance deployment configuration.

...

Xray calculated custom fields

...