Menu

Integration with Rally

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.

Setting up the Connection

  1. Go to Integration Settings on your qTest Manager instance.
  2. Click the Add Connection button in the Connection List.
  3. Enter required information for the connection in the pop-up window, including Connection NameRally Server URL, and Admin Rally Account Credentials

    Add Connection Form

  4. Alternatively, you can log in with your Rally API key.
    • Access to [your Rally URL]/login/accounts/index.html#/keys to get the API key

    • Enter apikey in the Username field, and enter the API key in the Password field.

  5. Click the Test Connection button to check the server availability.
  6. Click the Save & Configure button after a successful connection test.
  7. You can start to configure integration with Rally for defects and requirements.
    • For a new Connection, the Configure Connection page will display after clicking the Save & Configure button.
    • For an existing Connection, click the Configure icon for that connection to open the Configure Connection page.
  8. After configuring Defect and Requirement Integration, click the Save & Activate button.
  9. Click the Refresh button of the Confirmation pop-up window.  Your new configured connection will be activated.  Note that the Activation Status is ON and your configured connection is checked as Active in Connection List.

    Confirmation_Pop-up.png

    Confirmation Pop-up Message

  10. 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.

  11. To edit your connection, click the Configure icon of that Connection in the Connection List.
  12. You can delete your Rally connection in the Connection List by clicking the Delete icon in the Actions column.

Configuring Defects with Rally

After you successfully set up the connection with your Rally OnDemand instance, you can set up defect integration with Rally OnDemand.

  • You can set Integration with multiple Rally projects.
  • You can only select Rally defects to map as qTest Manager Defects.
  • qTest Manager requires you to have at least one project and object type selected.
  • Mapped Rally objects will be treated as Defects in qTest Manager.

To configure Defects Integration with Rally:

  1. Go to the Configure Connection screen after a successul Connection set-up.
  2. In the Defect Integration, click Add Defect Type.

  3. Select Rally Project and Defect as Rally object type from the drop-down lists.

  4. In the Action column of Defect Integration's Mapping list, click the Configure icon to configure individual mapped Defects.
  5. 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..
    • Click the Reset Fields button to reload the latest Field Settings of mapped Rally defects.
    • Click the Repopulate icon in the Action colum of each Defect field to reload the latest values of individual fields from Rally.
    • Click the Delete icon to remove the display of specific fields from qTest Manager's defect submission form.  Those deleted fields will still be on the Rally form.
    • Click the Move Up and Down arrows to re-arrange the display of defect fields in the qTest Manager defect submission form.  Their positions remain unchanged in the Rally form.
    • Click the Add Field button to manually add fields that can't be automatically populated from Rally to qTest Manager.

    Edit_Auto_Filling_Form.png

  6. 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.
    • Select a defect field to open the Edit Field Screen.

      Select_Defect_Field_for_mapping.png

    • Edit the field as your own style, such as required or field type.
    • Check the Auto Fill option in Input Option or you can set Default Value for field.
    • Click the Add button to add the field for mapping.
    • Click the Drop-down button to select the qTest Manager field to map to the Rally field.
    • Click the OK button to finish your mapping configuration.

    Add_Auto-Fill_Value.png

HINTS:

  • The values of mapped input and output fields must be symmetric between Rally and qTest Manager.
  • Only Defect's 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

A. Configure Requirement Integration with Rally

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

  1. Turn the Activation of Requirement Integration feature on.
  2. Click the Add Requirement Type button.

  3. Select Rally projects and User Story as object type to retrieve. User stories from selected Rally projects will be imported into qTest as Requirements.

  4. Click the Configure icon to open the Edit Data Retrieval screen and configure for user stories in each selected Rally project.
  5. On the Edit Data Retrieval screen, qTest Manager displays all Rally's user story field. You can:
    • Select to retrieve get data from all Rally objects or from a query.  Click here for how to write a Rally query.
    • Check Active for Rally user story's fields you want to display on qTest Manager's Requirement pages.
    • Click the Refresh Fields Setting button to reload the latest field configuration from your Rally instance.

  6. You can either retrieve the data of all Rally user stories or from each project you map.
    • Click the Retrieve Rally Data button to populate the latest data of all mapped Rally user stories.
    • Click the Re-Populate icon to get the latest data of user stories from a specific project.

    • In a specific imported Rally user story in qTest Manager Requirements, click Retrieve data to reload the latest data of that Rally user story.

B. Viewing imported Rally user story on qTest Requirement

Imported Rally user stories will be 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:

  1. Rally imported requirements are represented by special integration icons Snap_2013-08-02_at_11.29.46.png,to differ from internal qTest Manager Requirements Snap_2013-08-02_at_11.30.36.png.
  2. An imported requirement from Rally has two Properties sections: Rally's Properties and qTest's Properties
    • Rally's Properties contain Active Rally user story fields configured on the Edit Data Retrieval screen. These Properties are Read-only.  qTest 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 get the updated + new user stories.  You have to Re-selectReload, or Refresh to get the updated data of Rally imported Requirements you are standing on.
  3. 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 Requirement which only retains the Description of the Rally object.
    • Moved issues' Properties will remain unchanged.
  4. Imported requirements can be associated to qTest Manager Test Cases.
  5. Rally IDs of imported requirements will be included in the Requirements and Test Execution Results Report.

C. 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.
  • Test Cases and their associations with User Stories will not be updated or removed in Rally, regardless of any changes in qTest Manager.
  • In the Rally Test Case, the link to the corresponding Test Case in qTest Manager is put in its Description field.

 

Retrieving Requirements using Rally Query Filter 

While configuring Requirement retrieval from Rally to qTest Manager, you can input a query to retrieve only the requirements which meet specific conditions.

To build a Rally query, follow these steps.

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

IMPORTANT:

  1. Date / time values need converting to UTC and reformatting to the correct form: yyyy-mm-dd’T’hh:mm:ss’Z’ (e.g., 2013-12-31T00:00:00Z).
  2. You cannot create a query with Release and Iteration names.  Please use their Object ID in the query.
    • The syntax is: Release.ObjectID = [Release ID] or Iteration.ObjectID = [Iteration ID]
    • To get the object ID of a Release/Iteration 1) Access to 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.  Click the Check Syntax button 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 through qTest Test Execution.

You can submit defects to Rally from qTest Manager during Test Execution or from the Test Log.

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

    Submit_Defect_to_Jira.png

  2. You can also click on the Bug icon in the Execution History and Test Log Details sections to create defects.

  3. Click the New button to create a new Defect.
  4. Select one of configured Rally projects to submit the Defect. 
  5. The Mapped Project will be attached before Defect Type and auto displayed in the Project drop-down list, corresponding to the selected Defect Type.

  6. The Defect Submission form will be loaded.
    • 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

    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 it will not be linked to the corresponding Test Run and User Story.

  7. The system will return Defect ID with Summary and the latest Defect Status from Rally attached to the Bug icon.

  8. 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 its Description field.
    • Links to the associated Rally's User Story and Test Case.

HINT: You can download the browser plugins for the supported browsers from the qTest Resources page.

Subscribe To Our Blog
Powered by Zendesk