Menu

Pulse Constants

Overview

Pulse Constants are static values that are used in the Pulse Rules program code. This article provides instructions on where to locate the Constants information along with how to enter them in qTest Pulse.

The Pulse Constants listed below are used in the Pulse Rules outlined 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.

Below are the Constants for which you will gather information:

  • constants.qTestAPIToken
  • constants.ManagerURL
  • constants.Scenario_Account_ID
  • constants.Scenario_Project_ID
  • constants.JenkinsUserName
  • constants.JenkinsURL
  • constants.JenkinsJobName
  • constants.JenkinsJobToken
  • constants.JenkinsAPIToken

qTest API Token

The qTest API Token is used for the following Pulse Rules:

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.
    resources_page_API_token.jpg
  5. Navigate back to qTest Pulse and select the Constants tab.
  6. Select the Add Constant button.
  7. In the Name field, enter 'qTest API Token'.
  8. In the Value field, paste the Token string you copied from qTest Manager.
  9. Submit to save.

 Manager URL

The Manager URL is used 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: youcompanyname.qtestnet.com

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

Scenario_Account_ID and Scenario_Project_ID

The Scenario Account ID and Project ID are used for the following Pulse Rules:

The following Constants are located within your Jira project that you have configured for Scenario.

  1. Select the Jira project for which 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 (you will need to 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 have previously enabled the Enterprise Features when you configured Scenario.)
  6. Copy the Scenario Account ID and Scenario Project ID that display in their appropriate fields.
    enterprise_settings_tab_scenario.png
  7. Navigate back to qTest Pulse and select the Constants tab.
  8. Select the Add Constant button.
  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. Repeat steps 8-11 for the Scenario Project ID.

Jenkins Username 

The Jenkins Username is used for the following Pulse Rule:

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

Jenkins URL

The Jenkins URL is used 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 the Add Constant button.
  3. In the Name field, enter 'Jenkins URL'.
  4. In the Value field, paste the Jenkins URL from your browser.
  5. Submit to save.

Jenkins Job Name

The Jenkins Job Name is used 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 the Add Constant button.
  3. In the Name field, enter 'Jenkins Job Name'.
  4. In the Value field, paste the name of your Jenkins Job.
  5. Submit to save.

Jenkins Job Token

The Jenkins API Token is used 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 the Add Constant button.
  3. In the Name field, enter 'Jenkins Job Token'.
  4. In the Value field, paste the unique Authentication Token generated in the 'Build Triggers' setting of your Job.
  5. Submit to save.

Jenkins API Token

The Jenkins PI Token is used 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 the Add Constant button.
  3. In the Name field, enter 'Jenkins API Token'.
  4. In the Value field, paste the API token from the 'User Configuration' page.
  5. Submit to save.

 

Subscribe To Our Blog
Powered by Zendesk