The `artillery-plugin-slack` package provides a robust integration for Artillery.io, enabling users to send real-time test run notifications directly to a specified Slack channel. Currently at version 1.19.0 (last updated roughly 2 months ago), this plugin integrates seamlessly into Artillery's YAML test scripts. It publishes critical test summary information including whether a test run succeeded or failed, its total duration, the number of Virtual Users (VUs) completed, any encountered errors, and a direct link to the test run's view in Artillery Cloud if applicable. Developed and maintained by the Artillery team, its release cadence is tied to the main Artillery CLI, ensuring compatibility and continuous improvements. This plugin serves as a crucial component for CI/CD pipelines and monitoring setups, providing immediate feedback on performance test outcomes without needing to log into the Artillery dashboard.
npm install artillery-plugin-slackVerified import paths — ran on the pinned version, not inferred.
This Artillery YAML configuration demonstrates how to enable the `slack` plugin and provides a basic load test scenario. The Slack webhook URL is loaded from an environment variable for security, and two load phases are defined for a typical test workflow.
Ensure your Slack App is up-to-date with Slack's latest API requirements. Always use the latest stable version of `artillery-plugin-slack` and Artillery. Consult the Artillery and Slack documentation for migration guides related to API changes.
Check Artillery's main changelog and plugin release notes for specific fixes related to distributed testing status reporting. Ensure you are running a recent version of Artillery and `artillery-plugin-slack`. It has been noted that some fixes were introduced in Artillery CLI v2.0.24 and v2.0.12 concerning Slack plugin reporting.
Double-check that the `webhookUrl` in your Artillery configuration is correct, active, and has the necessary permissions in your Slack workspace. It's recommended to store this URL in an environment variable (`${process.env.SLACK_WEBHOOK_URL}`) for security and easier management.Verify that `artillery-plugin-slack` is installed correctly, either globally (`npm install -g artillery-plugin-slack`) or as a local dev dependency (`npm install --save-dev artillery-plugin-slack`). Ensure the plugin name `slack` is correctly nested under `plugins:` in your YAML configuration.
Upgrade to the latest versions of Artillery CLI and `artillery-plugin-slack`. This issue has received attention and fixes in recent Artillery releases. Verify the Artillery Cloud dashboard for the definitive test status.
Ensure `webhookUrl` is correctly configured in your Artillery YAML. Validate the webhook URL in Slack settings and confirm network connectivity from where Artillery is executed. Enable `DEBUG=plugin:slack` to check for specific errors during plugin execution.
Install the plugin globally (`npm install -g artillery-plugin-slack`) if Artillery is installed globally, or as a local dev dependency (`npm install --save-dev artillery-plugin-slack`) if Artillery is installed locally within your project. Ensure the installation path is accessible.