Slack

How to configure Slack webhooks in ContextQA so your team receives test run summaries and critical failure alerts in the right channels.

Who is this for? SDETs, developers, and engineering managers who want their team to receive test run results and failure alerts in Slack — without polling the ContextQA dashboard.

Slack notifications allow ContextQA to push test run summaries and failure alerts to the Slack channels your team is already monitoring. Instead of requiring engineers to poll the ContextQA dashboard, results are delivered automatically when a run completes or when a critical failure occurs.

ContextQA Bug Reporting integration category showing Jira, Slack, Linear, Freshrelease, YouTrack, Mantis, Backlog, Zepel, and Bugzilla cards

---

Configuring Slack webhooks in ContextQA

Slack notifications use Incoming Webhooks — a standard Slack feature that gives ContextQA a URL to post messages to a specific channel.

Step 1: Create a Slack Incoming Webhook

1. Go to your Slack workspace's app directory: https://api.slack.com/apps
2. Create a new Slack app (or use an existing one) and enable Incoming Webhooks.
3. Click Add New Webhook to Workspace and select the channel where notifications should appear.
4. Copy the webhook URL — it will look like https://hooks.slack.com/services/T.../B.../...

Step 2: Add the webhook URL to ContextQA

1. In ContextQA, click the Settings icon in the left sidebar.
2. Navigate to the Plugin or Integrations section.
3. Find the Slack integration and enable it.
4. Paste the webhook URL into the Slack webhook URL field.
5. Save the configuration.

ContextQA will send a test message to the channel to verify the connection.

---

What triggers a Slack notification

ContextQA sends Slack notifications for the following events:

Event	Description
Test plan complete	Sent when a scheduled or manually triggered test plan finishes, regardless of result
Test plan failed	Sent when a test plan finishes with one or more failed test cases
Critical failure	Sent immediately when a high-priority test case fails, without waiting for the full plan to complete
Scheduled run complete	Sent after a scheduled nightly or periodic test run finishes

Notification events can be configured per workspace. Contact your ContextQA workspace administrator to adjust which events trigger notifications.

---

Message format

Each Slack notification includes:

• Run status — Passed, Failed, or Aborted, shown as a color-coded indicator (green for pass, red for fail)
• Test plan name — the name of the test plan or test suite that was run
• Summary counts — number of tests passed, failed, and skipped
• Execution duration — how long the run took
• Result link — a direct URL to the full execution report in ContextQA, including screenshots, video, and step logs
• Timestamp — when the run completed

For failure notifications, the message also includes:

• The name of the first failing test case
• The AI-generated root cause summary (if available)
• A direct link to the failure detail page

Example notification format:

❌ Test Plan: Checkout Flow — FAILED
3 passed · 2 failed · 0 skipped · Duration: 4m 12s
First failure: Payment confirmation step — Element not found
View results: https://app.contextqa.com/executions/abc123

---

Routing projects to different Slack channels

If your ContextQA workspace contains multiple projects (e.g., separate test suites for different products or teams), you can route notifications to different Slack channels by configuring a separate webhook URL for each project.

To set up per-project routing:

1. Create a dedicated Slack webhook for each channel (e.g., #qa-frontend, #qa-payments).
2. In ContextQA's integration settings, assign each webhook URL to the corresponding project or test plan.

This ensures that the frontend team's Slack channel only receives notifications about frontend test runs, and the payments team receives notifications relevant to their area — reducing noise for each team.

---

Using Slack alongside bug tracker integrations

Slack notifications and bug tracker integrations (Jira, Azure DevOps) work independently and can both be active at the same time. A typical workflow:

1. A test plan fails overnight.
2. ContextQA sends a Slack notification to #qa-alerts with a summary and result link.
3. A QA engineer reviews the result, confirms the failure is a real bug, and clicks Report Bug in ContextQA to create a Jira issue.
4. The Jira issue link is shared in #qa-alerts as a follow-up message for full traceability.

This workflow keeps the team informed immediately while maintaining a formal bug record in the project tracker.

Connect ContextQA to your CI/CD pipeline in 15 minutes. Book a Demo → — See the full integration walkthrough for your existing toolchain.