Import all of these sample rules directly into Pulse by using the "Import" feature within Pulse and the AllRules.json file included. All constants will need to be filled out for rules that you would like to use.
Fields with a $ and all caps that look like a variable must be updated
Example: In cucumberJenkinsExecuteShell.sh, please replace $YOUR_PULSE_RULE_EVENT_URL, $YOUR_TEST_CYCLE_ID, $YOUR_PROJECT_ID, etc
Set up rules with your own event and with these actions. Note, anything that uses constants.X will need your own constants value.
Finally, these are only samples. Some of the actions are not 100% robust in case of failure.
Each formatter will format raw test results into something the UpdateQTestWithFormattedResults action will understand. And example of what these formatted results look like can be found in the ExampleFormattedResults.json file. Attachments may be included within the formatted results as an array of attachment objects.
attachmentObject = {
name: step.name + " Attachment " + attCount,
"content_type": att.mime_type,
data: att.data
};
This takes raw Cucumber for Java .json surefire reports and formats them into a format that the auto-test-logs endpoint will understand. At the end of this action, the rule that uses the action "UpdateQTestWithFormattedResults" will be called
This takes raw Postman .json and formats them into a format that the auto-test-logs endpoint will understand. At the end of this action, the rule that uses the action "UpdateQTestWithFormattedResults" will be called
This takes raw Python PyTest .xml (JUnit style) results and formats them into a format that the auto-test-logs endpoint will understand. At the end of this action, the rule that uses the action "UpdateQTestWithFormattedResults" will be called
Jenkins Execution Post Shell Action Configuration for Cucumber for Java with .json output
Triggers a Jenkins Job using the API of Jenkins. Note that your jenkins instance needs to be configured to allow a remove trigger. Verify with CURL before using this action from Pulse.
Sends a message to slack. A webhook must be set up in slack so you can send info to a channel or person.
This uses the auto-test-logs endpoint to bulk upload test cases, test runs, and test logs to qTest Manager. It also attempts to tie requirements to test case if the names match.
This sets the color coding in scenario for pass/fail at the start of the script.
This is action code to create a test case in qTest in the default API Creation qTest Test Design Module called 'Created via API'. The expected payload is the standard Jira webhook payload. This rule is used in conjunction with LinkRequirement.js and is intended to be used when a Jira Issue is created or modified to meet certain criteria (such as a status called Ready To Develop or something triggering wanting a default test case).
This is action code to link an existing qTest Test Case object, by object id, to a Jira requirement by Jira Issue Key. This assumes the Jira & qTest integration is already set up and that Jira Issue already exists in qTest as a requirement. CreateTestCase.js uses this action/rule, but it could be used independetly. The payload expected is a json object outlining the test case objectid and the Jira requirement Issue Key.
