Microsoft Teams Integration

Connect BugBrain to Microsoft Teams to receive real-time notifications about test executions, failures, and important events directly in your Teams channels.

What Can You Do?

Real-Time Notifications

Get instant updates in Teams:

• Test execution started/completed
• Test failures with details
• Discovery session completed
• Team member activities
• Quota usage alerts

Rich Message Cards

Beautiful, actionable notifications:

• Visual status indicators (✅ ❌ ⚠️)
• Test details and screenshots
• Quick action buttons
• Direct links to BugBrain
• Formatted error messages

Channel-Based Routing

Send different notifications to different channels:

• Critical failures → #alerts
• Daily summaries → #qa-reports
• Discovery results → #testing
• Team activities → #dev-updates

Setting Up Teams Integration

Prerequisites

You need:

• Microsoft Teams workspace
• Permission to add connectors/webhooks
• Admin or owner role in BugBrain
• Available on all plans (including Starter)

Method 1: Incoming Webhook (Recommended)

Step 1: Create Incoming Webhook in Teams

1. Open Microsoft Teams
2. Go to the channel where you want notifications
3. Click ••• (More options) next to channel name
4. Select Connectors or Workflows
5. Search for “Incoming Webhook”
6. Click Configure or Add
7. Name it “BugBrain Notifications”
8. Upload an icon (optional)
9. Click Create
10. Copy the webhook URL (you’ll need this!)

Step 2: Add Webhook to BugBrain

1. Go to BugBrain → Settings → Integrations
2. Click Connect next to Microsoft Teams
3. Paste your webhook URL
4. Give it a name (e.g., “QA Alerts Channel”)
5. Click Connect
6. BugBrain will send a test message to Teams

Step 3: Verify Connection

Check your Teams channel for a test message from BugBrain. If you see it, you’re all set!

Method 2: Microsoft App (Coming Soon)

Native Microsoft Teams app with advanced features:

• OAuth authentication
• Interactive messages
• Thread replies
• User mentions
• Adaptive cards

Status: Currently in development. Webhook method is fully functional.

Configuring Notifications

Choose What to Send

Select which events trigger Teams notifications:

Test Execution:

• ✅ Test passed
• ❌ Test failed
• ⚠️ Test had warnings
• 🔄 Test execution started
• ⏱️ Test timed out

Discovery:

• 🔍 Discovery session completed
• 📊 Discovery analysis ready
• 🚨 Critical issues found

Team Activity:

• 👤 New team member joined
• 📝 Test case created/updated
• 🗂️ Project created
• 🎯 Test plan scheduled

System Alerts:

• 📈 Quota usage warnings (80%, 90%, 100%)
• ⚠️ Integration errors
• 💰 Billing updates
• 🔒 Security alerts

Configure events:

1. Settings → Integrations → Microsoft Teams → Configure
2. Check events you want to receive
3. Save settings

Filter by Priority

Only get notified for important tests:

Priority filters:

• Critical only - Only P0 tests
• High and Critical - P0 and P1 tests
• Medium and above - P0, P1, P2
• All tests - Every test result

Configure:

1. Settings → Integrations → Teams → Filters
2. Select priority threshold
3. Apply per channel (if multiple)
4. Save

Filter by Project

Send notifications from specific projects:

1. Settings → Integrations → Teams → Filters
2. Select “Choose projects”
3. Check projects to include
4. Save settings

Use case: Create different webhooks for different channels, each watching specific projects.

Filter by Tags

Route notifications based on test tags:

Example setup:

• Tests tagged “smoke” → #alerts channel
• Tests tagged “regression” → #qa-updates
• Tests tagged “production” → #prod-monitoring

Configure:

1. Create multiple Teams connections (one per channel)
2. For each connection, set tag filters
3. Tests matching tags go to that channel

Message Format

Test Failure Notification

❌ Test Failed

Test: Login with invalid credentials
Project: Production App
Priority: High
Duration: 12s

Error: Element not found: button[data-testid="login"]

View Details → [Link to execution]
Rerun Test → [Quick action]
Create Issue → [Create Jira ticket]

Test Success Notification

✅ Test Passed

Test: Complete checkout flow
Project: E-commerce Site
Duration: 45s

View Details → [Link]

Discovery Complete Notification

🔍 Discovery Session Completed

Website: https://app.example.com
Pages Found: 47
Flows Detected: 12
Duration: 8m 32s

📊 Summary:
- 8 login flows
- 4 CRUD patterns
- 23 forms detected

View Full Report → [Link]
Generate Tests → [Quick action]

Daily Summary (Optional)

📊 Daily Test Summary

Date: January 15, 2026

✅ Passed: 142 (94%)
❌ Failed: 9 (6%)
⏱️ Avg Duration: 23s

🔥 Top Failures:
1. Login test (3 failures)
2. Checkout flow (2 failures)

View Analytics → [Link]

Customizing Messages

Message Templates

Customize notification content:

1. Settings → Integrations → Teams → Message Templates
2. Select notification type
3. Edit template using variables
4. Preview changes
5. Save template

Available variables:

• {{testName}} - Test case name
• {{projectName}} - Project name
• {{status}} - Pass/Fail/Warning
• {{duration}} - Execution time
• {{error}} - Error message
• {{priority}} - Test priority
• {{executionUrl}} - Link to BugBrain
• {{screenshots}} - Failure screenshots

Example custom template:

🚨 {{status}} - {{priority}} Priority

{{testName}}
{{projectName}}

{{error}}

Duration: {{duration}}
[View Details]({{executionUrl}})

Quiet Hours

Pause notifications during off-hours:

1. Settings → Integrations → Teams → Quiet Hours
2. Enable quiet hours
3. Set time range (e.g., 10 PM - 7 AM)
4. Select timezone
5. Choose days (e.g., weekdays only)
6. Save

During quiet hours:

• Notifications are held (not sent)
• Summary sent when quiet hours end (optional)
• Critical alerts can still come through (optional)

Multiple Channels Setup

Why Use Multiple Channels?

Different teams need different information:

• #alerts - Critical failures only
• #qa-daily - All test results
• #dev-team - Project-specific updates
• #stakeholders - High-level summaries only

Setting Up Multiple Webhooks

1. Create webhook in each Teams channel
2. In BugBrain, add each webhook as separate connection
3. Configure filters for each:
   • Alerts channel: Critical priority only, all projects
   • QA channel: All priorities, test execution events
   • Dev channel: Specific project, all events
4. Name connections clearly (e.g., “Teams - Alerts Channel”)

Routing Example

Setup for 3 channels:

#critical-alerts:

• Priority: Critical only
• Events: Test failures, timeouts
• Projects: Production only
• Quiet hours: Never

#qa-team:

• Priority: All
• Events: All test executions, discovery
• Projects: All
• Quiet hours: 10 PM - 7 AM

#dev-notifications:

• Priority: High and above
• Events: Failures only
• Projects: Development, Staging
• Tags: regression, smoke
• Quiet hours: Weekends

Quick Actions

Enable quick actions in Teams messages:

Rerun Test

Click button in Teams to rerun failed test:

1. Enable “Quick Actions” in integration settings
2. Test failure notifications include “Rerun” button
3. Click button in Teams
4. Test starts immediately
5. Get new notification with results

Create Issue

Create Jira/Trello issue from Teams:

1. Requires Jira or Trello integration
2. Click “Create Issue” in notification
3. Opens BugBrain (or creates automatically)
4. Issue linked to test execution

Mute Test

Temporarily mute notifications for flaky test:

1. Click “Mute” in notification
2. Test notifications paused for 24 hours
3. Unmute anytime in BugBrain settings

Best Practices

Advanced Features

Threaded Conversations

Group related notifications:

Enable threading:

1. Settings → Integrations → Teams → Advanced
2. Enable “Use threads”
3. Choose thread grouping:
   • By test case
   • By test plan
   • By execution batch
   • By project

Benefit: Related notifications appear in same thread instead of cluttering channel.

@Mentions

Notify specific team members:

Auto-mention rules:

• Test owner when their test fails
• On-call person for critical failures
• Project lead for project-wide issues
• Team when daily summary sent

Configure:

1. Settings → Integrations → Teams → Mentions
2. Add mention rules
3. Map BugBrain users to Teams users
4. Save rules

Example: When “Login Test” fails, mention @john-doe in Teams.

Scheduled Reports

Send regular reports to Teams:

Report types:

• Daily summary at 9 AM
• Weekly report on Mondays
• End-of-sprint report
• Monthly metrics

Configure:

1. Settings → Integrations → Teams → Reports
2. Enable scheduled reports
3. Choose report type and frequency
4. Select target channel
5. Customize report content

Troubleshooting

Not Receiving Notifications

Check these:

• Verify webhook URL is correct
• Check event filters in BugBrain settings
• Ensure tests are actually running
• Verify quiet hours aren’t active
• Check Teams channel settings

Test connection:

1. Settings → Integrations → Teams
2. Click “Send Test Message”
3. Check Teams channel

Webhook URL Invalid Error

• Webhook URL should start with https://
• Must be a Microsoft Teams webhook URL
• Format: https://yourcompany.webhook.office.com/...
• Try regenerating webhook in Teams

Messages Look Broken

• Ensure you’re using latest webhook connector
• Check message template syntax
• Verify variables are correctly formatted
• Try resetting to default template

Duplicate Notifications

• Check if multiple webhooks point to same channel
• Verify filter settings don’t overlap
• Review project-level integration settings
• Disable unused webhook connections

Security & Privacy

Data sent to Teams:

• Test names and descriptions
• Execution results and status
• Error messages
• Project names
• User names (who ran tests)

Data NOT sent:

• Passwords or credentials
• API keys or secrets
• Billing information
• Unrelated test data

Webhook security:

• Webhook URLs are encrypted in BugBrain
• Only accessible to org admins
• Can be regenerated anytime in Teams
• Rotate regularly for security

Rate Limits

Microsoft Teams limits:

• 200 messages per minute per webhook
• BugBrain automatically throttles to stay within limits
• If limit reached, messages queue and send when available

BugBrain recommendations:

• Use priority filters to reduce volume
• Enable quiet hours
• Use daily summaries instead of individual notifications for low-priority tests

Quota & Limits

Integration limits by plan:

Next Steps

• Set up Slack integration for additional channels
• Configure Jira integration for issue tracking
• Set up webhooks for custom workflows
• Learn about notifications