Zephyr Scale Test Management for Jira

eazyBI for Jira

Zephyr Scale - Test Management for Jira is a full-featured test management solution, seamlessly integrated into Jira's user interface. From a central location, coordinates all testing activities, including test planning, authoring, execution, tracking and reporting. Supports REST API integration with test automation tools to submit test results to Test Management For Jira.

Test Management for Jira is an app developed by SmartBear.

Data Import

If you have installed Zephyr Scale - Test Management for Jira then in Jira import options you will see the Zephyr Scale option or for versions prior eazyBI version 6.4 you will see an option with the former naming Test Management for Jira (TM4J) or Adaptavist Test Management (ATM).

Limit imported test executions

To reduce import time and the testing data in the cube, you can import only the most recent test executions.

Set a relative time limit for test executions like 3 months to import tests execution from the last three months or a particular date like Jun 14 2020  to set a date range from that date until now. Test executions are imported if they are created (test is added to the cycle) within the time limit (for scheduled test executions) or actual start date is within the time limit (for executed or in progress test executions). If there is no limit set, then all test executions are imported.

You can set a limit to all eazyBI accounts through advanced settings. 

# parameter name for eazyBI version 6.2 and 6.3
[jira.tm4j]
test_executions_limit = "3 months"

Since eazyBI version 6.4, the parameter name is changed to jira.zephyr_scale.

# parameter name starting eazyBI version 6.4
[jira.zephyr_scale]
test_executions_limit = "3 month"

Another option is setting the limit for an individual eazyBI account. In the import options, add the period in the field "Imported Test Execution limit". 

If there are import limits applied for the whole eazyBI instance using advanced setting, then the limit in import options won't exceed the limit in advanced settings. In such a way, the overall limits can be set on the eazyBI account, and, in an individual account, this time can be reduced more.

Dimensions

After the import the following Zephyr Scale specific dimension will be added:

Measures

The following Zephyr Scale-specific measures are imported. These measures can be analyzed by mentioned Zephyr Scale specific dimensions and by a few standard dimensions, Time, Project, and Fix Version. Note that, the measures used in the report define the context of standard dimensions and represent the project, component, or version of tests cases or test cycles.

For example, when using execution-related measures, like, Zephyr Scale Execution time, Zephyr Scale Test Cases executed, Zephyr Scale Test Cases with Test Cycles, and others, then standard dimension Project and Fix Version represent data on Test Cycle.

Properties

The following Zephyr Scale specific properties will be created.

Issue properties

Dimensions Zephyr Scale Defect, Zephyr Scale Requirement, and Zephyr Scale Test Cycle Related Issue are Jira issues which are also represented in the Issue dimension. You can define calculated measure to get any issue property that is imported in eazyBI also for those three Zephyr Scale specific dimensions. To access issue property, use function get(). For example, to get priority for Zephyr Scale Defect, copy a formula of issue property Issue Priority and replace dimension name [Issue] with [Zephyr Scale Defect] like this:

[Priority].[Priority].getMemberNameByKey(
  [Zephyr Scale Defect].CurrentHierarchyMember.get('Priority ID')
)

Another example, to get resolution date for Zephyr Scale Requirement, copy a formula of issue property Issue resolution date and replace dimension name [Issue] with [Zephyr Scale Requirement] like this:

[Zephyr Scale Requirement].CurrentHierarchyMember.get('Resolved at')

Add Issue hierarchy

You can group issues representing linked requirements and defects by Epic hierarchy or any other hierarchy you have built for the Issue dimension.

Additional hierarchies for Zephyr Scale dimensions are defined in eazyBI advanced settings (or site settings for Cloud) and are marked with the setting [[jira.zephyr_scale.custom_hierarchies]]. Provide the dimension name for which to enable the hierarchy, the hierarchy name, and the top-level member name. List all hierarchy levels where the bottom level is a requirement/defect issue (sub-task level is not supported).

For example, enable Epic hierarchy for the "Zephyr Scale Defect" dimension with three hierarchy levels: project of defect issue, Epic related to defect issue, and defect issue.

[[jira.zephyr_scale.custom_hierarchies]]
dimension = "Zephyr Scale Defect"
hierarchy = "Epic"
all_member_name = "All Defects by Epics"
levels = [
  {name="Project",key_column = "project_key"},
  {name="Epic",key_column="epic_key"},
  {name="Defect"}
]

If you already have constructed an additional Issue hierarchy, you can enable it also for Xray dimensions. Suppose you have a Features by Stories hierarchy as described in this example Separate hierarchy level for Story between parent and epic. Specify the dimension name for which to make the hierarchy, the hierarchy name, and the top-level member name. The levels should match the additional issue hierarchy description except for the Sub-task level and no parameters for the lowest (requirement or defect) level.

[[jira.zephyr_scale.issue_hierarchies]]
dimension = "Zephyr Scale Requirement"
hierarchy = "Features by Stories"
all_member_name = "All Issues by Features"
levels = [
  {name="Feature",key_column="customfield_featuree",issue_type="Feature"},
  {name="Epic and risk",key_column="customfield_epice",issue_type="Epic"},
  {name="Story",key_column="customfield_storye",issue_type="Story"},
  {name="Requirement"},
] 

You can enable the Plans hierarchy as well. In that case, list all hierarchy levels and parent keys matching the hierarchy configuration in Jira. The example below describes the Plans hierarchy for Initiative → Epic → Story and enables it to the "Zephyr Scale Requirement" dimension.

[[jira.zephyr_scale.custom_hierarchies]]
dimension = "Zephyr Scale Requirement"
hierarchy = "Plans"
all_member_name = "All requirements by Initiatives"
levels = [
  {name="Initiative",key_column = "jpoh_parent_3"},
  {name="Epic",key_column="jpoh_parent_2"},
  {name="Story"}
] 

Sample reports

If you selected the Import sample reports option, then additional sample reports are created in the Samples Zephyr Scale folder. Please try these reports to see which measures would be useful for your specific needs. If you would like to customize some reports, then save them and change the name (as the default sample reports are overwritten during each Jira import).