Menu

Integration with Rally

Overview

qTest Rally integration helps build a seamless bridge between Rally and qTest Manager. qTest Manager currently supports integration with Rally OnDemand for submitting Defects to Rally and import Requirements from Rally.  You can add as many connections with Rally OnDemand but only one connection will be active at a time.

Set up the Connection

  1. In your qTest Manager instance, access your  Integration Settings.
    Integration_Settings.png
  2. In the left navigation panel, under "External Systems," select Rally. The "Configure Integration: Rally" page displays.
  3. Select the +Add Rally (On-demand) Connection icon.
  4. In the dialog, enter the required information for the connection:
    • Connection Name
    • Rally Server URL
    • Admin Rally Account Credentials
      Add_Connection_dialog.png
  5. Select the Test Rally (On-demand) Connection icon to make sure that your connection has been successful.
  6. If successful, select Save & Configure. 

Add Connection Form

Alternatively, you can log in with your Rally API key. Follow these steps:

  1. Access to [your Rally URL]/login/accounts/index.html#/keys to get the API key
  2. Enter apikey in the Username field, and enter the API key in the Password field.

  3. Select the Test Connection icon to check the server availability.
  4. Select Save & Configure after a successful connection test.

You can now start to configure integration with Rally for defects and requirements. For a new Connection, the Configure Connection page will display after selecting Save and Configure.

For an existing Connection, follow these steps:

  1. Select the Configure icon for that connection to open the "Configure Connection" page.
  2. Configure the Defect and Requirement integration.
  3. Select Save and Activate.

 

Select Refresh in the "Confirmation" dialog. Your newly configured connection will be activated. Note: the Activation Status is ON and your configured connection is checked as "Active" in Connection List.

Confirmation_Pop-up.png

Confirmation Pop-up Message

After your Rally Connection Integration is successfully activated, a green status label indicating "in use" will be displayed next to Rally (OnDemand) and the Defect menu will be hidden.  Thus, the only way to submit a defect is through Test Execution.

To edit your connection, select the Configure icon in the Connection List.

You can delete your Rally connection in the Connection List by selecting the Delete icon in the Connection List.

Configure Defects with Rally

After you set up the connection with your Rally OnDemand instance, you can set up defect integration with Rally OnDemand. You are able to do the following:

  • Set up integratio wit multiple Rally Projects
  • Select Rally Defects to map as qTest Manager Defects

Note: 

  • qTest Manager requires you to have at least one project and type selected
  • Mapped Rally Objects will be treated as Defects in qTest Manager

To Configure your Defects Integration with Rally, please follow these steps:

  1. After a succesful Connection set up, navigate to the "Configure Connection" page.
  2. In "Defect Integration," select Add Defect Type
  3. Select both the Rally Project and Defect as the Rally Object types from the drop-down menus.

  4. In the Action column of the Defect Integration's Mapping list, select the Configure icon. Here, you can configure individual mapped defects.

 

  1. In the Action column of Defect Integration's Mapping list, select the Configure icon to configure individual mapped Defects.

The Edit Auto-Filling form displays. By default, qTest Manager will load all available fields of the mapped Rally defect onto the Defect Field column. Users can do the following:

  • Select Reset Fields to reload the latest Field Settings of mapped Rally Defect
  • Select the Repopulate icon in the Action column of each Defect Field to reload the latest values of individual fields from Rally
  • Select the Delete icon to remove the display of specific fields from the qTest Manager's defect submission form
    • Note: Those deleted fields will still be on the Rally form
  • Select the Move up or Down arrows to re-arrange the display of defect fields in the qTest Manager defect submission form
    • Note: Their positions remain unchanged in the Rally form
  • Select the Add Field icon to manually add fields that can't be automatically populated from Rally to qTest ManagerEdit_Auto_Filling_Form.png

Now, Set Auto-Filling for mapped Rally defect's fields. qTest Manager will auto-fill data from the Test Run or Test Case into mapped Rally defect's field as settings. Follow these steps:

  1. Select a defect field to open the Edit Field ScreenSelect_Defect_Field_for_mapping.png
  2. Edit the field as you like.
  3. Select the Auto fill option from the "Input Option" section, or, set the Default Value for the field.
  4. Select the Add icon to add the field for mapping.
  5. Select the Drop-down menu to select the qTest Manager field to map to the Rally field.
  6. Select OK to finish your mapping configuration.Add_Auto-Fill_Value.png

Hints:

  • The values of mapped input and output fields must be symmetrical between Rally and qTest Manager
  • Only Defect fields in Text format can be auto-filled
  • You can select to fill multiple qTest Manager fields into one Rally field

Retrieving Requirements from Rally

Configure Requirement Integration with Rally

You can optionally turn on Requirement Integration to retrieve Rally user stories and import them into qTest Manager as REquirements. To specify which Rally Projeects and user stories to be retrieved as qTest Requirements, perform the following steps:

  1. Turn the Activation of Requirement Integration feature on.
  2. Select the Add REquirement Type icon.
  3. Select Rally Projects and User Story as the Rally Object type. User Stories from selected Rally projects will be imported into qTest and Requirements.
  4. Select the Configure icon to open the "Edit Data Retrieval" page, nd configure for User Stories in each selected Rally Project.
  5. On the "Edit Data Retrieval" page, qTest Manager displays all Rally's User Story fields. Here, you can:
    • Select to retrieve data from all Rally objects or from a query. Refer to this article for instructions on how to write a Rally Query.
    • Select Active for Rally User Stories' fields you ant to display on qTest Manager's REquirement pages.
    • Select the REfresh Fields Setting icon to reload the latest field configuration from your Rally instance.
  6. You can either retrieve the data from all Rally User Stories or, from each Project that you map. To do so:
    • Select the REtrieve Rally Data icon to populate the latest data of all mapped Rally User Stories.
    • Select the Re-populate icon to get the latest data from User Stories from a specific Project.

  7. In your qTest Manager REquirements, from within a specific Imported Rally User Story, select Retrieve data to reload the latest data of that Rally User Story.

Viewing Imported Rally User Stories From Within qTest Requirements

Imported Rally User Stories are treated as Requirements in qTest Manager. By default, these integrated Requirements are loaded into a common Module folder named "Imported from Rally" as shown below. IMPORTANT:

 

  • Rally imported Requirments are represented by special integration icons
    Snap_2013-08-02_at_11.29.46.png
  • An imported Requirement from Rally has two Properties sections: Rally Properties and qTest's Properties.
    • Rallly's properties contain Active Rally User Story fields configured on the "Edit Data Retrieval" page. These Properties are Read-only. qTet Properties contain all qTest Requirement fields, excluding Description.
    • Currently, Rally fields CANNOT be used to Search or Query in qTest Manager.
    • qTest Manager will poll Rally every two minutes to pull both the updated and new User Stories. You have to Re-select, Reload or Refresh to fetch updated data from Rally imported Requirements you are standing on.
  • Imported Rally User Stories can be copied or moved across Modules within a qTest Manager Project to re-organize Module Structure.
    • Copied issues will become a qTest Requirements that only retains the Description of the Rally object.
    • Moved issues' Properties remain unchanged.
  • Imported Requirements can be associated with qTest Manager Test Cases
  • Rally ID's for imported Requirements will be included in the Requirements and Tests Execution Results Report.

Linking qTest Manager Objects with Requirements Imported from Rally

When a Test Case is created and linked to a Requirement imported from Rally into qTest Manager, a Test Case is also automatically generated and linked to that User Story in Rally.IMPORTANT:

  • Although qTest Manager allows linking a Test Case to multiple User Stories imported from Rally, Rally limits one Test Case's association to only one User Story. Thus only the first associated USer Story will be displayed in that Test Case in Rally.
  • Tests Casesa and their associated with User Stories will not be updated or removed in Rally, regardless of any change in qTest Manager.
  • In the Rally Test Case, the link to the corresponding Test Case in qTest Manager is put in its Description field.

Retrieve Requirements using Rally Query Filter

While configuring Requirement retrieval from Rally to qTest manager, you can input a query to retrieve only the Requirements that meet specific conditions.To build a Rally query, follow these steps:

  1. From Rally, define a new custom view of User Stories or select an existing one.
  2. Copy the custom view' conditions. Only select the text before "Sorted" as shown below.
  3. Replace the field's display name by its system name. Select the Rally field name lookup link to view the mapping between display names and system names.

IMPORTANT:

  • Date/time values need convertin to UTC and reformatting to the correct form: yyy-mm-dd"T'hh:mm:ss'Z' (e.g., 2013-12-31T00:00:00Z).
  • You cannot create a query with RElease and Iteration names. Please use their Objct ID in the query.
    • The syntax: Release.ObjectID + [RElease ID] or Iteration.ObjectID = [Iteration ID]
    • To get the Object ID of a Release/Iteration:
      1. Access its detailed page in Rally
      2. From the URL, the last string of numbers is the Object ID
        • For example: Release.ObjectID = 6039563204
  • You will need to append time values (e.g., 00:00:00Z) to the end of date values.
  • For example, the conditions (Name contains US) AND (Creation Date >= 2013-Dec-31) will be re-written as (Name contains US) AND (CreationDate >= 2013-12-31T00:00:00Z).
  • Fill in the query. Select Check Syntax to make sure your query is correct.

Submitting Defects to Rally

For Integration with external Defect Tracking Systems, the only way to submit Defects is from within qTest Test Execution.

You can submit Defects to Rally from qTest Manager during Test Execution, or, from the Test Log. Follow these steps:

  1. Select the Bug icon linked to Test Steps or Submit Defect linked to a Test Run in the TestPad.new_defect_new_test_pad_UI_overview.png

You can also select the Bug icon in the Execution History and Test Log Detail sections to create Defects. Follow these steps:

  1. Select the New icon to create a new Defect.
  2. Select one of the configured Rally Projects to submit the Defect.

The Mapped Project will be attached before Defect Type and auto-displayed in the Project drop-down list, corresponding to the selected Defect Type.

The Defect Submission form displays.

  • If you have the qTest Integration Browser Plugin installed, qTest Manager will open the Rally Create Defect form. You are required to login before submitting defects.
  • If you DO NOT install the browser plugin, qTest Manager will open the qTest Defect Submission form with integrated fields from Rally. Defect Fields will be auto-filled as configured.rally_Defect_Submission_form.png

IMPORTANT: When submitting a defect, two windows/tabs will be open: the Dashboard and the Defect Submission form. Please do not close the dashboard. If it is closed, the defect is still submitted successfully, but will not be linked to the corresponding Test Run and User Story.

The System will return Defect ID with Summary and the latest Defect Status from Rally attached to the Bug icon.
rally_Defect_Link.png

Review Rally Defect After Submission

The following links will be displayed in the Defect Page in Rally:

  • The link to the corresponding Test Run in qTest Manager is put in the Description field.
  • Links to the associated Rally User Story and Test Case.
    rally_Links_in_Defect.pngHINT: You can download the browser plugins for the supported browsers from the qTest Resources page.

Review Rally Defects in Manager

In qTest Test Execution, you can find Rally defect information in many areas:

Test Run page:

  • To view Rally defects in a particular Test Log, select the defect icon from the Execution History grid.
  • For an aggregate list, select the Defects tab for a roll-up of all Rally defects related to any of the test logs of the Test Run. The Defects tab can be customized so you can display additional Rally Defect fields as columns. 

Test Suite, Cycle, and Release pages:

  • To view Rally defects for a single Test Run, select the Defect icon from the Test Run grid.manager_defect_single.png

  • For an aggregate list, select the Defect Summary tab for a roll-up of all Rally defects related to associated Test Runs. This Defect Summary tab can be customized so that you can display additional Rally Defect fields as columns. 
    manager_defect_list.png

For advanced reporting, use qTest Insights to gain more defect visibility. 

Powered by Zendesk