Currents Documentation
Currents.devGitHubChangelog
  • Getting Started
    • What is Currents?
    • Playwright
      • Playwright: Quick Start
      • Troubleshooting Playwright
    • Cypress
      • Your First Cypress Run
      • Integrating with Cypress
        • Compatibility
        • Alternative Cypress Binaries
      • Troubleshooting Cypress
    • Jest
      • Your First Jest Run
      • Detox + Jest
      • Troubleshooting Jest
    • Others
    • CI Setup
      • GitHub Actions
        • Cypress - GitHub Actions
        • Playwright - GitHub Actions
        • Jest - GitHub Actions
        • Node.js - GitHub Actions
        • Commit data for GitHub Actions
        • Custom Docker runners
        • Named Runners
      • GitLab
        • Cypress - GitLab CI/CD
        • Playwright - GitLab CI/CD
        • Custom Docker runners
      • Jenkins
        • Cypress - Jenkins
        • Playwright - Jenkins
      • CircleCI
        • Cypress - CircleCI
        • Playwright - CircleCI
      • Bitbucket
        • Cypress - Bitbucket Pipelines
      • Azure DevOps
        • Cypress - Azure DevOps
        • Playwright - Azure DevOps
      • AWS Code Build
        • Cypress - AWS Code Build
        • Playwright - AWS Code Build
      • NX
        • Playwright - NX
        • Cypress - NX
  • Guides
    • Record Key
    • CI Build ID
    • Reporting
      • Reporting Strategy
      • Reporting in CI
      • Step-Level Reporting
    • CI Optimization
      • Playwright Parallelization
      • Orchestration Setup
      • Fully Parallel Mode
      • Re-run Only Failed Tests
      • Cloud Spot Instances
      • Failing Fast
      • Load Balancing
    • Code Coverage
      • Code Coverage for Playwright
      • Code Coverage for Cypress
    • Currents Actions
      • Setup Currents Actions
      • Using Currents Actions
      • Reference
        • Conditions
        • Actions
    • Playwright Component Testing
    • Playwright Visual Testing
    • Playwright Annotations
    • Playwright Tags
    • MCP Server
  • Dashboard
    • Projects
      • Projects Summary view
      • Project Settings
      • Archive and Unarchive Projects
    • Runs
      • Run Status
      • Run Details
      • Commit Information
      • Tags
      • Run Timeouts
      • Cancelling Runs
      • Deleting Runs
      • Run Progress
    • Tests
      • Spec File Status
      • Test Status
      • Flaky Tests
      • Test History
    • Test Suite Explorer
      • Test Explorer
        • Tests Performance
      • Spec Files Explorer
        • Spec Files Performance
      • Errors Explorer
  • Automated Reports
  • Insights and Analytics
  • Administration
    • Email Domain Based Access
    • SSO SAML2.0
      • SAML2.0 Configuration
      • SCIM User Provisioning
      • IdP-initiated Sessions
      • JumpCloud
        • JumpCloud User provisioning
      • Okta
        • Okta User provisioning
      • Troubleshooting SSO
    • Billing & Usage
  • Billing and Pricing
  • Resources
    • Reporters
      • cypress-cloud
        • Batched Orchestration
        • Migration to Cypress@13
      • @currents/cli
      • @currents/playwright
        • Configuration
        • pwc
        • pwc-p (orchestration)
        • Playwright Fixtures
      • @currents/jest
      • @currents/node-test-reporter
      • @currents/cmd
        • currents api
        • currents upload
        • currents cache
        • currents convert
      • Data Format Reference
    • Integrations
      • GitHub
        • GitHub App
        • GitHub OAuth
      • GitLab
      • Slack
      • Microsoft Teams
      • HTTP Webhooks
      • Bitbucket
    • API
      • Introduction
      • Authentication
      • API Keys
      • Errors
      • Pagination
      • API Resources
        • Instances
        • Runs
        • Projects
        • Spec Files
        • Test Signature
        • Test Results
    • Data Privacy
      • Access to Customer Data
      • Data Retention
      • Cloud Endpoints
    • Support
Powered by GitBook
On this page
  • Enabling Slack integration
  • Grouping Slack messages
  • Filtering Slack notifications based on Tags
  • What events trigger notifications for Slack // Currents integration?
  • Disabling Slack integration
  • FAQ

Was this helpful?

  1. Resources
  2. Integrations

Slack

Send Playwright and Cypress tests results to Slack

PreviousGitLabNextMicrosoft Teams

Last updated 2 months ago

Was this helpful?

Currents integration with Slack allows posting test results of your Playwright or Cypress tests directly into Slack channels.

Enabling Slack integration

In order to enable Slack integration and share Playwright test results to Slack channels, follow the steps:

  • Navigate to "Manage Project" section for the selected project

  • Click "Add Integration", and select "Slack"

  • Enter the details of your Slack Integration and click "Save"

Provide the following details to finalize Slack integration, click "Save" to finish:

  • Failed Runs Only - enabling the toggle would only send results for failed runs.

  • Events (Optional) - specify events that will trigger the integration and send the results. Leaving this field blank activates all the events.

  • Branch Name Filter (Optional) - if specified, only send notifications for runs with branch names matching the pattern. Please note, that you must provide the branch name within the Run Details to activate filtering.

Grouping Slack messages

  • Single Notification for All Groups (Optional) – Enabling the toggle will send a single notification per run event, regardless of the number of groups.

Filtering Slack notifications based on Tags

  • Include only tagA or tagB: (tagA|tagB)

  • Exclude tagA andtagB: !(tagA|tagB)

  • Include only tags starting with production: production*

  • Include only tags starting with smoke- or prod-: (smoke-*|prod-*)

What events trigger notifications for Slack // Currents integration?

The following events trigger notifications for Slack integration.

Run Start

Triggered when a new run starts. If a run contains multiple groups, the notification will be triggered for each group.

Run Finish

Triggered when a run finishes its execution. If a run contains multiple groups, the notification will be triggered for each group.

Run Timeout

Triggered when a time out detected for a run. The message will contain the last known results for the run or run group.

Run Canceled

Triggered when a run gets cancelled. If a run contains multiple groups, the notification will be triggered for each group. The message will contain the last known results for the run or run group.

Disabling Slack integration

To disable Slack integration, simply delete the integration from the list of integrations.

FAQ

Can I have multiple Slack integrations for the same project?

Yes, you can have multiple Slack integrations for the same project.

What do notification status colours mean?

Green - passed tests

Red - failed + skipped tests

Grey - ignored tests

Purple - flaky tests

Slack Webhook URL - Incoming Webhook URL, e.g. https://hooks.slack.com/services/XXX/YYY/ZZZ. Read more about .

Please note: We use to evaluate the filters. Test your filtering rules using the . See examples for some popular filter patterns:

Slack Incoming Webhooks
glob patterns
playground
Tests Results in Slack Channel
Enabling Slack integration
Single Slack notification
Example of Slack notification for Run Start event
Example of Slack notification for Run Finished
Example of Slack notification for Run Finished with Timeout event
Example of Slack notification for Run Canceled event