Menu

Pulse Constants

Overview

The Pulse Rules program code uses static values called Pulse Constants. This article provides instructions on where to locate the Constants information, along with how to enter them in qTest Pulse.

Use the Pulse Constants below in the Pulse Rules which we outline in the Sample Scenario-BDD for Jira Workflow. This sample workflow lends a holistic view of how qTest Manager, Scenario, and Pulse integrates with Jira, Jenkins and your Git repository.

Gather the Constants information listed below:

  • constants.qTestAPIToken (v9.0)
  • constants.QTEST_TOKEN (v9.1)
  • constants.ManagerURL
  • constants.Scenario_Account_ID (v9.0)
  • constants.Scenario_Project_ID
  • constants.Scenario_URL (v9.1)
  • constants.JenkinsUserName
  • constants.JenkinsURL
  • constants.JenkinsJobName
  • constants.JenkinsJobToken
  • constants.JenkinsAPIToken
  • constants.SlackWebhook

qTest API Token

The following Pulse Rules use your qTest API Token:

To access this Constant information, do the following:

  1. From qTest Manager, select the Resources resources.jpg icon.
  2. The Resources page loads.
  3. Click to expand the API & SDK tab.
  4. Copy the string of characters located in the Token field.
    • Pulse 9.0 rules use the value present in the 'Token' field.
    • Pulse 9.1 rules use the value present in the 'Bearer Token' field but without the preceding 'bearer' token type. 
      api_tokens.png
  5. Navigate back to qTest Pulse and select the Constants tab.
  6. Select Add Constant.
  7. In the Name field, enter:
    • For Pulse 9.0 rules use qTestAPIToken
    • For Pulse 9.1 rules use QTEST_TOKEN
  8. In the Value field, paste the appropriate token string you copied from qTest Manager.
    • For Pulse 9.0 rules use Token.
    • For Pulse 9.1 rules use Bearer Token, but do not include the 'bearer' portion.
  9. Submit to save.

 Manager URL

Use your Manager URL for the following Pulse Rules:

The Manager URL is listed in your web browser search bar and is your qTest instance URL. It is unique to your organization.
Example: yourcompanyname.qtestnet.com

  1. In qTest Pulse, select the Constants tab.
  2. Select Add Constant.
  3. In the Name field, enter 'ManagerURL.'
  4. In the Value field, paste the Manager URL from your browser.
  5. Submit to save.

Scenario Account ID 

Use your Scenario Account ID for the following Pulse 9.0 Rules, as this value is deprecated for Pulse 9.1:

Find the following Constants within your Jira project that you have previously configured for Scenario.

  1. Select the Jira project where you are using Scenario.
  2. Navigate to the Settings tab for the Jira project.
  3. Select the qTest Scenario add-on located at the bottom of the Jira Project Settings column (use the scroll bar within the column, not the window.)
    qTest_Scenario_add_on_inside_of_jira_project_settings.png
  4. The Project Settings window loads.
  5. Select the Enterprise Settings tab (this is assuming you had previously enabled the Enterprise Features when you configured Scenario.)
  6. Copy the Scenario Account ID that displays.
    enterprise_settings_tab_scenario.png
  7. Navigate back to qTest Pulse and select the Constants tab.
  8. Select Add Constant.
  9. In the Name field, enter 'Scenario_Account_ID.'
  10. In the Value field, paste the value you copied from Jira.
  11. Submit to save. 

Scenario Project ID

Use your Scenario Account ID for the following Pulse 9.0 and 9.1 Rules:

Find the following Constants within your Jira project that you have previously configured for Scenario.

  1. Select the Jira project where you are using Scenario.
  2. Navigate to the Settings tab for the Jira project.
  3. Select the qTest Scenario add-on located at the bottom of the Jira Project Settings column (use the scroll bar within the column, not the window.)
    qTest_Scenario_add_on_inside_of_jira_project_settings.png
  4. The Project Settings window loads.
  5. Select the Enterprise Settings tab (this is assuming you had previously enabled the Enterprise Features when you configured Scenario.)
  6. Copy the Scenario Account ID that displays.
    scenario_project_ID.jpg
  7. Navigate back to qTest Pulse and select the Constants tab.
  8. Select Add Constant.
  9. In the Name field, enter 'Scenario_Account_ID.'
  10. In the Value field, paste the value you copied from Jira.
  11. Submit to save. 

Scenario URL

Use the Scenario URL for the following Pulse Rules:

  1. In qTest Pulse, select the Constants tab.
  2. Select Add Constant.
  3. In the Name field, enter 'Scenario_URL'.
  4. In the Value field, paste this URL:
     https://9box-scenario.qtestnet.com/api/
  5. Submit to save.

Jenkins Username 

Use your Jenkins Username for the following Pulse Rule:

  1. In qTest Pulse, select the Constants tab.
  2. Select Add Constant.
  3. In the Name field, enter 'JenkinsUsername'.
  4. In the Value field, paste the username you use to login to Jenkins.
  5. Submit to save.

Important: Make sure your Jenkins username does not contain any white spaces on either side of the value when entering in as a Constant.

Jenkins URL

Use your Jenkins URL for the following Pulse Rule:

The Jenkins URL is listed in your web browser search bar and is your Jenkins instance URL.

  1. In qTest Pulse, select the Constants tab.
  2. Select Add Constant.
  3. In the Name field, enter 'JenkinsURL.'
  4. In the Value field, paste the Jenkins URL from your browser.
  5. Submit to save.

Important: Make sure your Jenkins URL does not contain any white spaces on either side of the value when entering in as a Constant.

Jenkins Job Name

Use your Jenkins Job Name for the following Pulse Rule:

The Jenkins Job Name is the name given to the project that builds and executes your automated tests.
Jenkins_job_Name.png

  1. In qTest Pulse, select the Constants tab.
  2. Select Add Constant.
  3. In the Name field, enter 'JenkinsJobName'.
  4. In the Value field, paste the name of your Jenkins Job.
  5. Submit to save.

Important: Make sure your Jenkins Job Name does not contain any white spaces on either side of the value when entering in as a Constant.

Jenkins Job Token

Use your Jenkins API Token for the following Pulse Rule:

The Jenkins Job Token is the Authentication Token that enables triggering the build remotely.
jenkins_job_token.png

  1. In qTest Pulse, select the Constants tab.
  2. Select Add Constant.
  3. In the Name field, enter 'JenkinsJobToken'.
  4. In the Value field, paste the unique Authentication Token generated in the 'Build Triggers' setting of your Job.
  5. Submit to save.

Important: Make sure your Jenkins Job Token does not contain any white spaces on either side of the value when entering in as a Constant.

Jenkins API Token

Use your Jenkins API Token for the following Pulse Rule:

The Jenkins API Token is a Jenkins generated code that authenticates a remotely triggered build.

  1. In qTest Pulse, select the Constants tab.
  2. Select Add Constant.
  3. In the Name field, enter 'JenkinsAPIToken.'
  4. In the Value field, paste the API token from the 'User Configuration' page.
  5. Submit to save.

Important: Make sure your Jenkins API Token does not contain any white spaces on either side of the value when entering in as a Constant.

Slack Webhook

Use your Slack Webhook for the following Pulse Rule:

  • Slack Action

The Slack Webhook is generated by your organization's Slack environment. You will also need to choose the Slack Channel where you want your notifications to update. Read this article for information on how to access your Slack webhook.

  1. In qTest Pulse, select the Constants tab.
  2. Select Add Constant.
  3. In the Name field, enter 'SlackWebhook.'
  4. In the Value field, paste the Slack Webhook you retrieved from your Slack instance.
  5. Submit to save.

 

Powered by Zendesk