Link and Report Scenario Results in qTest Manager

This 'Pulse Rule' sample allows you to report and view Scenario test progress in qTest Manager by linking your Scenario requirements to qTest Manager.

Please note, Tricentis does not include an exception for calls made by Pulse in our API Gateway controls due to the open-ended nature of qTest Pulse's design. When the servers are under a period of high load, you may receive rate limit error messages, or 429s, from the qTest API during Pulse's regular operation. This is to ensure API stability. If you have any questions, please contact support@tricentis.com.

Pulse Rules

UpdateqTestAndScenarioWithFormattedResults.js

Set up 'Rules' for your own 'Trigger' (webhook) and use the sample 'Actions' provided below.

Setup Pulse Rule

  1. Review the qTest Pulse Quick Start Guide for your version of Pulse for complete instructions on how to add Pulse Triggers, Actions, and Rules.

  2. Enter the sample Program Code in the Pulse Actions.

    For the most up-to-date sample program code, view the Pulse Rules repository.

Constants

Anything that uses constants.X will need your own constants value.

Pulse Rules

  • constants.qTest_TOKEN

  • constants.ManagerURL

Variables

Pulse Rules

Variables do not need to be updated for Pulse by the user.

UpdateScenarioWithResults.js

Set up 'Rules' for your own 'Trigger' (webhook) and use the sample 'Actions' provided below.

Setup Pulse Rule

  1. Review the qTest Pulse Quick Start Guide for your version of Pulse for complete instructions on how to add Pulse Triggers, Actions, and Rules.

  2. Enter the sample Program Code in the Pulse Actions.

    For the most up-to-date sample program code, view the Pulse Rules repository.

Pulse Constants

Anything that uses constants.X will need your own constants value.

  • constants.qTest_TOKEN

  • constants.SCENARIO_PROJECT_ID

Variables

None

LinkScenarioRequirements.js

Set up 'Rules' for your own 'Trigger' (webhook) and use the sample 'Actions' provided below.

Setup Pulse Rule

  1. Review the qTest Pulse Quick Start Guide for your version of Pulse for complete instructions on how to add Pulse Triggers, Actions, and Rules.

  2. Enter the sample Program Code in the Pulse Actions.

    For the most up-to-date sample program code, view the Pulse Rules repository.

Constants

Anything that uses constants.X will need your own constants value.

Pulse Rules

  • constants.Scenario_URL

  • constants.qTest_TOKEN

  • constants.Scenario_Project_ID

  • constants.ManagerURL

Variables

Pulse Rules

Variables do not need to be updated for Pulse by the user.