Search…
⌃K

Zephyr (Enterprise Level) Integration

Mapping Zephyr Test Cases with Avo Assure Scenarios

  1. 1.
    Log in to Avo Assure. Click on the 'Integration' Plugin on the landing page.
Avo Assure – Landing Page
2. Click on the ‘Zephyr’ icon on the Integration page.
Integration page
3. Click on the ‘Zephyr’ icon, Zephyr login pop-up will be displayed (if Zephyr Configuration is not done or invalid data is provided at the User Settings).
NOTE: If valid Zephyr Configuration is done at the User Settings, skip the next Step.
Zephyr login pop up
4. Zephyr login can be done in two ways:
  • Basic Login:
    • Zephyr URL
    • Zephyr Username
    • Zephyr Password
    Enter the above details and click on the 'Submit' button.
Zephyr Integration login details
  • Token-based login (Recommended when Zephyr SSO is enabled):
    • Zephyr URL
    • Zephyr API Token
    Enter the above details and click on the 'Submit' button.
Zephyr Integration login details
5. On Successful Zephyr login, the following screen is displayed.
Avo Assure - Zephyr mapping page
Note: The left block depicts Zephyr tests' details and the right block depicts Assure scenarios.
6. Select the Zephyr test case by navigating through the project and release. Then map the selected Zephyr test to the selected Avo Assure scenario by clicking on the ‘Synchronize’ and ‘Save’ button.
Avo Assure – Zephyr mapping
7. Once the mapping is done, click on 'View Mapped Files' button. The user will be able to view all mappings made between the Zephyr Tests and Avo Assure Scenarios. Click on the 'i' icon for any Zephyr test case.
Avo Assure – Zephyr View Mapped Files Screen
8. The requirement details of the Zephyr test case will be displayed, on click of the ‘i’ icon.
Zephyr test case requirement details
Note: If the requirement is not mapped to Zephyr Test Case as mentioned in the Prerequisites section, then a pop up with the following message will be displayed.
Zephyr test case requirement details
9. To go back to map other Zephyr tests with Avo Assure scenarios, click on the Zephyr icon in the Action bar.
10. Click on the ‘Exit’ button to exit from the Zephyr Integration screen. This will navigate the user to the landing page of the Integration screen.
11. Then from the task list, navigate to a module/scenario execution task which is mapped with the Zephyr test.
Avo Assure – Landing Page task list
12. In Execution Screen, select the scenarios checkbox and click on any browser icon. Then ‘Select Integration’ dropdown will be enabled.
Execution page
13. Choose ‘Zephyr’ option from the ‘Select Integration’ dropdown. If valid Zephyr Configuration is done at the User Settings, skip the next Step.
14. In the Zephyr Login pop up, enter the valid URL and credentials. There are two ways to login:
  • Basic login contains:
    • Zephyr URL
    • Zephyr Username
    • Zephyr Password
    Enter the above details and click on the 'Save' button.
Execution page – Zephyr login pop up
  • Token-based login contains (Recommended when Zephyr SSO is enabled):
    • Zephyr URL
    • Zephyr API Token
    Enter above details and click on ‘Save’ button.
Execution page – Zephyr login pop up
15. On Execution completion/termination, the status of executed scenarios (that were mapped) will be updated in Zephyr.
16. ICE console will display the following message:
ICE log for status update

Types of Mapping

Following three types of synchronization are provided in Zephyr Integration:
  1. 1.
    One Zephyr test to One Avo Assure Scenario (1-1)
(1-1) Zephyr-Avo Assure mapping
2. One Zephyr test to Multiple Avo Assure Scenarios (1-N)
(1-N) Zephyr-Avo Assure mapping
3. Multiple Zephyr tests to One Avo Assure Scenario (N-1)
(N-1) Zephyr-Avo Assure mapping
NOTE: Multiple entries of Zephyr test cases/ Assure scenarios can be selected using ‘Ctrl’ key.

Import Mappings

Avo Assure provides its users, the ability to map Zephyr Test Cases (belonging to a specific phase/module) and Avo Assure Scenarios in bulk. This is done by importing an excel file that contains the Zephyr Test Case IDs along with the respective Avo Assure Scenarios to be mapped.
NOTE:
  • The first row of the excel sheet is considered as a header which should contain the titles: “TestCaseId”, for the column specifying the Zephyr Test Case IDs and “Scenario”, for the column specifying the Avo Assure Scenario names. The titles are case insensitive.
  • In case a user wants to map multiple Zephyr Test Case IDs to one Avo Assure Scenario or one Zephyr Test Case ID to multiple Avo Assure Scenarios, then multiple values can be provided in the cell by separating these values using a semicolon (;).
Example of the data within an excel sheet for importing mappings:
Zephyr Import Mappings Excel Sheet Sample
To import Zephyr to Avo mappings via an excel sheet, perform the following steps:
  1. 1.
    Login to Avo Assure, click on 'Integration' Plugin from the landing page.
Avo Assure – Landing Page
2. Click on the ‘Zephyr’ icon on the Integration page.
Integration page
3. On click of ‘Zephyr’ icon, if valid Zephyr configuration is provided at the User Settings, then the landing page of Zephyr will be displayed else the Zephyr login pop up will be displayed for the user to provide valid data.
Zephyr login pop up
4. On Successful Zephyr login, click on the ‘Import Mappings’ icon from the left panel (Action Bar).
Avo Assure - Zephyr mapping page
5. The ‘Import Mappings’ pop up will be displayed. Click on ‘Upload file’.
NOTE: Only excel files can be imported.
Zephyr Mapping Page – Import Mappings – ‘Upload Excel File’
6. Select the sheet name, the Zephyr project and its release.
Import Mappings – Select sheet name, Zephyr Project and Release
7. Now select the phase/module for which the mappings are being imported from the structure displayed.
Import Mappings – Select phase/module
8. After the phase/module selection, select the Avo Assure project.
Import Mappings – Select Avo Assure Project
9. Click on the ‘Import’ button.
10. If all the mappings are successfully imported a message stating “Successfully imported!” will be displayed.
Import Mappings – Import Successful
11. If any of the rows in the provided excel sheet are invalid OR a Zephyr Test Case ID is not found in the selected phase/module OR an Avo Assure Scenario is not found in the selected Avo Assure project, then the user will be prompted about these details.
Import Mappings – Import Partially Successful

Update mapping of Mapped Zephyr Test Cases

If the Zephyr test cases existing for a particular release/cycle/phase are to be reused, the Zephyr user can copy and paste these test cases to a different release/cycle/phase. This can result in, Zephyr test cases having the same name but different ID.
When execution is performed via Avo Assure after Zephyr integration is selected, this will update the execution results for the initial release/cycle/phase. For the execution results to be populated in the updated release/cycle/phase, remapping of existing test cases needs to be performed.
Remapping of existing test cases can be done by performing the following steps:

Prerequisites:

When Zephyr test cases in the new location need to be mapped to the already mapped Avo Assure scenarios, then the Zephyr test cases in the new location must have the same name as the old Zephyr test cases.
  1. 1.
    Log in to the Zephyr Integration Screen successfully and click on the ‘Update Mappings’ button.
Zephyr Mapping Page
2. The ‘Update Mapping’ Screen will consist of two sections:
Zephyr – Update Mapping Page
  • Left Section ‘Mapped Zephyr Test Cases’: This section will display the Zephyr test cases that are already mapped.
  • Right Section ‘Zephyr Folder Structure’: This section will display the existing folder structure of the logged-in Zephyr instance.
3. From the left section of ‘Mapped Zephyr Test Cases’, select the test case(s) whose mappings are to be updated.
Update Mapping Page – Selecting test cases
Note: All test cases within the Release/Cycle/Phase can be selected at once by checking the checkbox against the required Release/Cycle/Phase.
4. After all required test cases to be updated are selected, on the right section of ‘Zephyr Folder Structure’, select the Phase to which the test cases must be found and mapped to.
Update Mapping Page – Selecting phase
5. Click on the ‘Update’ button.
Update Mapping Page – Updating after selections
Once the update is completed, the mapping will be created and saved based on the following criterions:
  1. 1.
    If all the Zephyr test cases with the same names are found at the updated folder location (hierarchy), then all the previous mappings will be overwritten by mappings from the Zephyr test cases at the new location to the previously targeted Avo Assure scenarios.
Successfully updated found test cases
2. If multiple Zephyr test cases with the same names are found at the updated folder location (hierarchy), then,
  • the found test cases (unique) will be mapped from the new location to the previously targeted Avo Assure scenarios,
  • the multiple found test cases will be NOT be mapped, and these Zephyr test cases will be shown in the pop-up under the ‘No matches found’ section
  • The user will be notified of the above events.
Update failed due to multiple test having same names
3. If Zephyr test cases with the same names are not found at the updated folder location (hierarchy), then
  • The found test cases will be mapped from the new location to the previously targeted Avo Assure scenarios, and
  • The Zephyr test cases that are unavailable will be shown in popup under ‘Not Found’ section.
  • The user will be notified of the above events.
Update failed because test cases (with same names) were not found

Unsync Mapped Files

  1. 1.
    In ‘View mapped files’ screen, the mapped files can be unsynced in two different ways:
  • Single Avo Assure scenarios can be selected and unsynced after clicking ‘unsync’ button
  • Single Zephyr tests can be selected and can be unsynced after clicking on ‘unsync’ button
Unsync Zephyr Test
2. Click on ‘Save’ button, after unsyncing the mapped files to reflect the changes.
Unsync Avo Assure Scenario
NOTE: Multiple entries of Zephyr tests/ Assure scenarios can be selected using ‘Ctrl’ key.