Menu

Color Code Scenario Results in Jira

Overview

This 'Pulse Rule' sample sets the color coding in Scenario for pass/fail at the start of the script. It then logs into qTest manager and uses the auto-test-logs endpoint to bulk upload test cases, test runs, and test logs to qTest Manager. The final step is that it attempts to link requirements (you must have requirements already mapped and integrated from JIRA to qTest Manager) with the new test cases.

  • Passed=Green
  • Skipped=Yellow
  • Failed=Red

Pulse Rules v9.0

Pulse Rules v9.1-Coming Soon!

scenarioColors.js

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

Setup Pulse Rule

  1. Review the 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. 
    Note: For the most up to date sample program code, view the QASymphony/PulseRules repository linked above.

Constants

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

  • constants.Scenario_Account_ID
  • constants.Scenario_Project_ID

Variables

None

UpdateQTestAndScenarioWithFormattedResults.js

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

Setup Pulse Rule

  1. Review the 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. 
    Note: For the most up to date sample program code, view the QASymphony/PulseRules repository linked above.

Constants

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

  • constants.qTestAPIToken
  • constants.ManagerURL

Variables

Fields with a $ and all caps that look like a variable must be updated.

Example: In UpdateQTestAndScenarioWithFormattedResults.js, please replace $YOUR_SLACK_EVENT_NAME

 

Powered by Zendesk