Two approaches to get notifications with the Test Cycle execution status and outcomes automatically pushed to your Slack Channel
If a project within your Worksoft SaaS domain is integrated with Slack, you can receive (get pushed) the Test Cycle execution status notifications (along with key details about the outcomes of the test runs with the test cycle) to the Slack Channel(s) that are integrated with a specific project.
There are two approaches you can use to accomplish the same (automatic pushing of test cycle execution details to your Slack Channel(s).
a) Manually Trigger the push of the Test Cycle execution detail to your Slack Channel using the 'Action' icon from within the Test Cycles module home screen. This is similar to how you can get an email notification sent ad hoc from the Test Cycles module home screen. To know more on how to utilize this approach, please click here.
You may also get the notification by using the Slack "Slash" Command for Test Cycle through Slack.
/cycle<SPACE><TestCycleIdentifier>
Note: There might be a chance of having the same Test Cycle in multiple projects. In such cases, you may need to give the command as the below-mentioned format:
/cycle<SPACE><TestCycleIdentifier><SPACE>project<SPACE><ProjectName>
Steps to copy the Test Cycle Identifier:
/cycle<SPACE><TestCycleIdentifier>
Note: There might be a chance of having the same Test Cycle in multiple projects. In such cases, you may need to give the command as the below-mentioned format:
/cycle<SPACE><TestCycleIdentifier><SPACE>project<SPACE><ProjectName>
Steps to copy the Test Cycle Identifier:
Step 1: Login to Worksoft SaaS.
Step 2: Select a Project, where you will be navigated to the Test Runs screen.
Step 3: Click Menu and Click Test Cycles.
Step 4: Click on the below icon to copy the Test Cycle Identifier.
b) Indicate your preference to get an automated Slack message posted to your Slack Channel when you make calls to one of three QaCONNECT REST Services that operate on a test cycle
Please note that if you would rather want to pull (retrieve) the test cycle execution and outcome details into your Slack Channel from within your Slack Channel, you will be able to do that as well. For that, you have to use the Slack Slash Command supported by the Worksoft SaaS Slack App. For more details on this approach, please click here. The difference between this approach and other approaches described in this article is that the slash commands allow you to pull information down when you are already in the Slack Channel context from Worksoft SaaS whereas the two approaches described in this article don't require you to post a request from within the Slack Channel but expect you to have specified your interest in receiving automatically posted messages to your Slack Channel while making a call to the QaCONNECT REST Service or when using the Test Cycles module home screen within the Worksoft SaaS application.- Schedule Call: As you know, you use this service to schedule test runs to be executed within a specific test cycle. Right at the time of scheduling, you can specify your preference to get a notification automatically posted (pushed) to your Slack Channel when the test cycle execution completes.
- Mark Complete: As you know, you use this service to mark the completion of execution of test runs that will be executed within a specific test cycle and that you will NOT schedule any more test runs within the same test cycle. Right at the time of calling this service, you can specify your preference to get a notification automatically posted (pushed) to your Slack Channel.
- Get Execution Status: As you know, you use this service to retrieve the current status of the Test Cycle. Right at the time of calling this service, you can specify your preference to get a notification automatically posted (pushed) to your Slack Channel. Please click here for details on the QaCONNECT REST Services that pertain to the services listed above.
You can use either or both approaches to accomplish the same end goal of retrieving the details about the status and outcome of test cycle execution.
The Result:
Please note that you get the same exact response back irrespective of the 2 approaches described in this article (or even the pull approach described outside of this article) you follow. You decide which approach(es) is (are) best suited for your needs.
As you can see from the screenshot above, the response includes more or less the same detail that is currently included in the (push) email notifications about the execution status and outcome of test cycles, if you opted and configured for the same to get sent out at the test cycle level.