Slack Integration with Automation
By integrating Automation with Slack, you can use a dedicated Slack channel to automatically notify internal team members about important test results in real-time. You can also define the type of test results you want to share. To create a Slack integration with Automation, you will need Slack admin rights for your Slack workspace.
Post Messages on Slack via Automation
Step 1: Create a Webhook.
- Create a new Slack app in the workspace where you want to post messages by selecting Add an app.
- From the Features page, toggle and activate Incoming Webhooks.
- Click Add New Webhook to Workspace.
- Pick a channel for the app to post to, then click Authorize.
- Use the Incoming Webhook URL to post a message to Slack.
Please see the screenshots below.
Above: Adding an app in the workspace.
Above: Activating Incoming Webhooks.
When Incoming Webhooks are added from the app directory, you can see a Webhook URL generated for your channel.
Above: View of the generated Webhook URL.
Step 2: Add a new web service connection in Automation.
Create your test script with the connection details given below.
Above: Adding a new web service connection.
Step 3: Create a Test Script.
Create a test script. Drag the Web Request API from the Test Palette and drop it to your test script. Enter everything after the Slack API in the webhook URL to the Resource URL section.
Enter the text that you want to post in the body section in the given below format.
Above: Creating a test script.
Now, execute your test script. By default, the username with which your messages will be incoming and the channel name to which the messages are posted are set in the Incoming Webhooks configuration, but you can update the details in the JSON payload as well.
Upload file to a Slack Channel
You can upload a file to a Slack channel using Slack Files upload method API.
Step 1: Generate an authentication token by Creating a new Slack app and installing it in your workspace. Your tokens are displayed after installation is completed.
Above: Generating an authentication token.
Step 2: Add a new web service connection in Automation.
Above: Adding a new web service connection.
Create a new script with the connection drag Web Request API from the Test Palette and drop to the test script.
Add a new Part
Enter the channel name as a parameter in the Resource URL and enter the authentication code in the Request Header in the format below.
Authorization:Bearer xoxp-27633*******-************-*************-************************
Enter the file’s name in the File Name section and add the file to be uploaded.
Above: Uploading the file.
Now, run your test script.
- Provar Automation
- Installing Provar Automation
- Updating Provar Automation
- Using Provar Automation
- API Testing
- Behavior-Driven Development
- Creating and Importing Projects
- Creating Test Cases
- Custom Table Mapping
- Functions
- Debugging Tests
- Defining a Namespace Prefix on a Connection
- Defining Proxy Settings
- Environment Management
- Exporting Test Cases into a PDF
- Exporting Test Projects
- Override Auto-Retry for Test Step
- Managing Test Steps
- Namespace Org Testing
- NitroX
- Provar Desktop
- Provar Test Builder
- Refresh and Recompile
- Reintroduction of CLI License Check
- Reload Org Cache
- Reporting
- Running Tests
- Searching Provar with Find Usages
- Secrets Management and Encryption
- Setup and Teardown Test Cases
- Tags and Service Level Agreements (SLAs)
- Test Cycles
- Test Plans
- Testing Browser Options
- Tooltip Testing
- Using the Test Palette
- Using Custom APIs
- Callable Tests
- Data-Driven Testing
- Page Objects
- Block Locator Strategies
- Introduction to XPaths
- Creating an XPath
- JavaScript Locator Support
- Label Locator Strategies
- Maintaining Page Objects
- Mapping Non-Salesforce fields
- Page Object Operations
- ProvarX™
- Refresh and Reselect Field Locators in Test Builder
- Using Java Method Annotations for Custom Objects
- Applications Testing
- Provar Manager
- DevOps
- Introduction to Test Scheduling
- Apache Ant
- Configuration for Sending Emails via the Automation Command Line Interface
- Continuous Integration
- AutoRABIT Salesforce DevOps in Provar Test
- Azure DevOps
- Running a Provar CI Task in Azure DevOps Pipelines
- Configuring the Automation secrets password in Microsoft Azure Pipelines
- Parallel Execution in Microsoft Azure Pipelines using Multiple build.xml Files
- Parallel Execution in Microsoft Azure Pipelines using Targets
- Parallel execution in Microsoft Azure Pipelines using Test Plans
- Bitbucket Pipelines
- CircleCI
- Copado
- Docker
- Flosum
- Gearset DevOps CI/CD
- GitHub Actions
- Integrating GitHub Actions CI to Run Automation CI Task
- Remote Trigger in GitHub Actions
- Parameterization using Environment Variables in GitHub Actions
- Parallel Execution in GitHub Actions using Multiple build.xml Files
- Parallel Execution in GitHub Actions using Targets
- Parallel Execution in GitHub Actions using Test Plan
- Parallel Execution in GitHub Actions using Job Matrix
- GitLab Continuous Integration
- Travis CI
- Jenkins
- Execution Environment Security Configuration
- Provar Jenkins Plugin
- Parallel Execution
- Running Provar on Linux
- Reporting
- Salesforce DX
- Git
- Team Foundation Server
- Version Control
- Salesforce Testing
- Best Practices
- Troubleshooting
- Release Notes