Integration with QTM4J 4x

Integrate QTM4J 4x with QAS

You can upload the QAS execution results to other products of QMetry product suite. This document describes integration of QMetry Automation Studio with QMetry Test Management for Jira 4x.

First you need to integrate QMetry Automation Studio with QMetry Test Management for Jira 4x.

 

Steps:

1. Go to Project Settings.

2. Select TCM Integrations.

The TCM Integrations screen opens. If you already have integrations created before, they will be listed on the screen. If you do not have any integrations created yet, you can start creating the first one.

3. Click on the Create button on the screen.

The Create New Integration panel opens.

4. Enter the following details to create new integration for project:

  • Name: Enter integration name.

  • Type: Select either from the options: QTM4J Cloud, QTM4J Server.

The QTM4J Integration is added on the TCM Integrations screen. You can enable/disable the integration on the screen.

To configure parameters for the newly created integration, click on the Key.

The configuration screen opens with the list of properties.

Configure the QTM4J properties as per your QTM4J instance.

Refer to QTM4J Cloud Help for more details on configuration parameters for QTM4J Cloud.

Refer to QTM4J Server Help for more details on configuration parameters for QTM4J Server.

Activate QTM4J Integration

Make sure you activate/enable the QTM4J Integration that you want to use to import the test execution into QTM4J.

If you have multiple integrations, you can mark multiple integration enabled. While execution/publishing the test results, you will be asked to select either of them.

Auto Publish Test Cycle Execution Result

You can link an existing active QTM4J integration with individual test cycle from the test cycle details page in the Test Cycle module in QAS. Only those integrations, which are enabled in the TCM Integration section, will appear on the list.

The integrations are configured from Project Settings > TCM Integrations.

Once the QTM4J integration is linked with the test cycle, then the results will be automatically published in respective QTM4J instance as soon as the execution is complete. Alternatively, you can also link the QTM4J integration from the Analytics module to publish the individual execution.

Steps:

To enable the QTM4J integration with the test cycle, click on the icon at the top.

 

 

 

Now run the job or the cycle.

The success message pops up indicating the execution has been started.

Publish Existing Test Cycle Execution Results to QTM

Users can publish the execution result against the integration from Analytics.

Steps:

1. Go to the Analytics module.

2. Select the job/cycle execution from the panel.

The execution details for job/cycle are displayed on the screen at right. You can see the icon to publish to TCM Integration.

3. Click on the icon, it asks to select integration from all the active integrations.

4. Select the required QTM4J Integration and click Publish at the bottom.

 

 

The success message pops up indicating the result has been published successfully.

View Test Results Published to QTM4J

Open the QTM4J instance that you configured for integration in QAS.

Open the Test Cycle module and check the newly added test cycle in the records.

Click on the Execute icon for the test cycle.

The execution details of test cases covered under the test cycle are displayed on the execution screen.

 

The test cases are also added to the Test Case module.

Delete Integration

To delete an integration, first disable the integration status of that integration.

Hover over the record, and click on the Delete icon for the integration.

 

The confirmation message pops up.

Click Yes to proceed.

View History

You can view the audit logs or history for the integration used by the test cycles from the TCM Integration screen.

Steps:

1. Go to Project Settings > Select TCM Integrations.

2. Click on the Key of QTM4J integration.

3. Open the History tab.

You can view the executions carried over for the selected QTM4J integration.