slackChannel flag - HYP

Author: amanchopra1905

docs/deep-dive-into-hyperexecute-yaml.md

@@ -814,6 +814,36 @@ project:
 
 ***
 
+### `slackChannel`
+
+This flag allows you to receive real-time notifications about your Job updates in a Slack channel of your choice, ensuring that your team stays informed about all the Job status directly within your preferred Slack workspace.
+
+:::note Prerequisites
+- To avail this feature, connect with our <span className="doc__lt" onClick={() => window.openLTChatWidget()}>Support Team.</span>
+- 📕 You must first [*integrate Slack*](https://www.lambdatest.com/support/docs/hyperexecute-slack-integration/) from the **Integration** section of the LambdaTest dashboard.
+:::
+
+After successfully integrating Slack, specify the Slack channel where you want Job updates to be sent by updating your HyperExecute YAML file:
+
+```yaml title="hyperexecute.yaml"
+slackChannel: hyperexecute-job-updates #slack channel name
+```
+> This feature does not work for **private** Slack channels.
+
+Or, if you prefer using variable:
+
+```yaml title="hyperexecute.yaml"
+slackChannel: ${channel}
+```
+
+And then in your CLI/terminal, pass your desired channel name like:
+
+```yaml
+./hyperexecute --vars "channel=hyperexecute-job-updates" #enter your slack channel name
+```
+
+***
+
 ### `differentialUpload`
 
 When you are working with relatively large codebases, and constantly updating and upgrading your test scripts. Getting them onto the HyperExecute platform for every run might consume extra time.

docs/hyperexecute-slack-integration.md

@@ -85,7 +85,30 @@ Once you integrate Slack, you need to configure notification settings to get tes
 - Update the **Notification Time** as well.
 - Now run the test and visit the Slack channel to view the build notification containing Job Number, Job Status, Executed By, Started At, Job Duration, Test Duration etc.
 
-## Step 4: Report a bug for a Failed Test
+## Receive Notification on Custom Slack Channels
+> - To avail this feature, connect with our <span className="doc__lt" onClick={() => window.openLTChatWidget()}>Support Team.</span>
+> - This feature does not work for **private** Slack channels.
+
+After successfully integrating Slack, specify the Slack channel where you want Job updates to be sent by updating your HyperExecute YAML file:
+
+```yaml title="hyperexecute.yaml"
+slackChannel: hyperexecute-job-updates #slack channel name
+```
+
+Or, if you prefer using variable:
+
+```yaml title="hyperexecute.yaml"
+slackChannel: ${channel}
+```
+
+And then in your CLI/terminal, pass your desired channel name like:
+
+```yaml
+./hyperexecute --vars "channel=hyperexecute-job-updates" #enter your slack channel name
+```
+
+
+## Report a bug for a Failed Test
 
 - Click on the failed test. It will navigate you to the automation page.
 - Click on the bug icon.

docs/hyperexecute-yaml-parameters.md

@@ -161,7 +161,8 @@ The **HyperExecute YAML** file serves as the foundational component for test exe
 | [alwaysRunPostSteps](/support/docs/deep-dive-into-hyperexecute-yaml/#alwaysrunpoststeps) | Boolean | Execute the Post Steps in every scenario case |
 | [cacheTestURL](/support/docs/deep-dive-into-hyperexecute-yaml/#cachetesturl) | Boolean |It enables users to cache static test files. |
 | [afterAll](/support/docs/deep-dive-into-hyperexecute-yaml/#afterall) | Map |It is used to run commands after the job has finished. |
-| [projectName](/support/docs/deep-dive-into-hyperexecute-yaml/#projectname) | String | Segregate data at a project/repo level |
+| [project](/support/docs/deep-dive-into-hyperexecute-yaml/#project) | String | Segregate data at a project/repo level |
+| [slackChannel](/support/docs/deep-dive-into-hyperexecute-yaml/#slackchannel) | String | Allows you to receive notifications of your Job updates directly in your preferred Slack channel. |
 
 <nav aria-label="breadcrumbs">
   <ul className="breadcrumbs">