Menu

Integration with VersionOne

qTest Manager's integration with VersionOne allows for teams to see full traceability between test runs, VersionOne requirements, and defects.

qTest Manager currently supports integration with VersionOne OnDemand for submitting Defects to VersionOne and import Requirements from VersionOne.  You can add as many connections with VersionOne OnDemand but only one connection is active at a time.

Setting up the Connection

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

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

    Confirmation_Pop-up.png

  9. After your V1 Connection integration is successfully activated, it will be notified with a green status label "in use" next to VersionOne (On-demand), and the Defect menu will be hidden. Thus, the only way to submit a defect is through Test Execution.

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

Configuring Defects with VersionOne

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

IMPORTANT:

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

To configure Defects Integration with V1

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

  3. Select VersionOne Project and VersionOne Object type from the drop-down lists.

  4. In the Action column of the 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 V1 object type onto the Defect Field column.
    • Click the Reset Fields button to reload the latest Field Settings of the mapped object type.
    • Click the Repopulate icon in the Action column of each Defect field to reload the latest values of individual fields from V1.
    • Click the Delete icon to remove the display of specific fields from the qTest Manager defect submission form.  Those deleted fields are still on the V1 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 V1 form.
    • Click the Add Field button to manually add fields that can't be automatically populated from V1 to qTest Manager.

    Edit_Auto_Filling_Form.png

Set Auto-Filling for mapped V1 object type's fields.  qTest Manager will auto-fill data from Test Run or Test Case into the mapped V1 object'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 a field for mapping.
  • Click the Drop-down button to select a qTest Manager field to map to V1 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 V1 and qTest Manager.
  • Only fields in Text format can be auto-filled.
  • You can select to fill multiple qTest Manager fields into one V1 field.

Retrieving Requirements from VersionOne

Configure Requirement Integration with VersionOne

Users can optionally turn the Requirement Integration feature on to retrieve V1 objects and import into qTest Manager as Requirements.

To configure, follow these steps:

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

  3. Select V1 projects and object types to retrieve.  Mapped V1 objects from selected V1 projects will be imported into qTest Manager as Requirements.

  4. Click the Configure icon to open the Edit Data Retrieval screen and configure for each V1 object type.
  5. On the Edit Data Retrieval screen, qTest Manager displays all V1 object fields of your selected type.  You can:
    • Check Active for V1 object fields you want to display on qTest Manager Requirement pages.
    • Click the Refresh Fields Setting button to reload the latest field configuration from your V1 instance.

  6. You can either retrieve data of all V1 object types or any specific types you map.
    • Click the Retrieve VersionOne Data button to populate the latest data of all mapped V1 object types.
    • Click the Re-Populate icon to get the latest data of a specific mapped V1 object type.

    • In specific imported V1 imported Requirements in qTest Manager, click Retrieve data to reload the latest data of that V1 object.

View Imported VersionOne Requirements

Imported VersionOne objects will be treated as Requirements in qTest Manager.  By default, these integrated requirements will be loaded into a common Module folder named "Imported from VersionOne" as shown below.

IMPORTANT:

  1. Imported V1 objects are represented by special integration icons to differ from internal qTest Requirements.Snap_2013-08-02_at_11.30.36.png
  2. An imported V1 object has two Properties sections - VersionOne's Properties and qTest's Properties
    • V1's Properties contain Active V1 object fields configured on the Edit Data Retrieval screen.  These Properties are Read-only.  qTest Properties contain all qTest Manager Requirement's fields, excluding Description.
    • Currently, V1 fields CANNOT be used to Search or Query in qTest Manager.
    • qTest Manager will poll V1 every two minutes to get the updated + new objects.  You have to Re-selectReload, or Refresh to get the updated data of V1 objects you are standing on.
  3. Imported V1 objects can be copied or moved across Modules within a qTest Project to re-organize Module Structure.
    • Copied objects will become qTest Requirements which only retain the Description of V1 objects.
    • Moved objects' Properties will remain unchanged.
  4. Imported V1 objects can be associated to qTest Manager Test Cases.
  5. V1 IDs of imported objects will be included in the Requirements and Test Execution Results Report

HINT:

  • An object in V1 has two different types of ID - the display ID and the OID.  Those IDs are displayed in qTest as shown below.

Linking Test Cases with VersionOne Requirements

Imported V1 objects can be linked to qTest Manager Test Cases.  The linking with qTest Manager Test Cases will be generated in the corresponding V1 object's Links section.

  • When you link or create associated Test Cases to an Imported V1 object, qTest Manager also generates a link under the corresponding V1 object.

Submitting Defects to VersionOne

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

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

    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 the configured V1 object types 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.

  5. The Defect Submission form will be loaded.
    • If you have the qTest Integration Browser Plugin installed, qTest Manager will open the VersionOne Defect form.  You must 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 V1.

      Defect fields will be auto-filled as configured

  6. The system will return the Defect ID with Summary from Rally attached to the Bug icon.

    HINT:

    • An object in V1 has two different types of ID - the display ID and the OID.  Those IDs are displayed in qTest as shown below.

  7. From V1, you can see the link to qTest Test Run in the Link section of the defect.

     

Subscribe To Our Blog
Powered by Zendesk