ZEPHYR Tool Configuration

Introduction

Zephyr for JIRA (Server and Data Center versions) is a application that resides in JIRA Software or JIRA Core and brings test management capabilities to any JIRA project. With the addition of Zephyr for JIRA, tests can be created and viewed in any JIRA project, linked to other issues, executed immediately or as part of a test cycle and detailed test metrics can be tracked via customized gadgets.

PSKnowHOW seamlessly integrates with Zephyr, enabling the derivation of crucial information pertaining to Regression and In-Sprint Automation test case executions. Beyond that, it serves as an invaluable tool for users, offering clear insights into test case associations with Stories, distinguishing between linked and unlinked test cases. Additionally, PSKnowHOW diligently monitors the count of defects linked with these stories, facilitating meticulous defect management throughout the software development process.

Open

User can follow below to integrate the tool-

Setup Configuration

• To setup, navigate to project settings and click 'Setup' under Zephyr tool.

  Open

  

   

Setup Configuration Details

• Under Zephyr Configuration page, first section shall be 'Available Connection'. Recently created Zephyr Connections shall be displayed here. Select radio button for desired connection.

• Configured Tool section shall display existing configuration with Bitbucket.

• Enter following details:

  • Project Key: Key used to uniquely identify a project in Jira. It is mandatory field.

  • Component: If Test cases and Defect use 'Component' as field then user can enter component value to identify those.

  • Label Values to identify Automated Regression Test Cases- If Test cases and Defect use 'Label Values' to identify Automated Regression cases.

  • Folder Path (In-Sprint Automation Coverage)- Folder path to identify test cases that are automated within a sprint.

  • Folder Path (Regression Automation Coverage)-Folder path to identify test cases that are automated for regression.

  • Test Case Automation Field- Name of the field which is used to identify test case automation. Ex- 'Execution Type'.

  • Values for Automation Exclusion- Provide all the values for which you want to exclude the test cases. ex-'Manual'

  • Test Case Automation Done Field- Name of the field which is used to identify if test case is automated or not. Ex- 'Is Automated'

  • Values for Automation Completed- These require values to identify if test case is automated. Ex- ‘Yes' or 'Y’

  • Test Case Regression Field (For Automated Test Cases)- Field to identify whether the test cases belongs to Sanity or Regression Suite. Ex- Sanity/Regression

  • Test Case Regression Field Value- This require values to enter for above field. Ex- 'Regression'

• Click Save 

Note: For the updated data to populate after user edit the configuration, tool processor needs to be run again by navigating Settings>Misc Setting.

Edit Configuration

Once Zephyr is configured, user can proceed with validating data populated on KPI. However In case, user anticipate any changes for tool configuration

• Navigate to the Settings> Project Name >Edit

• Under Zephyr , click Edit configuration

Note: For the updated data to populate after user edit the configuration, tool processor needs to be run again by navigating Settings>Misc Setting.