Notifications
Stay informed about test results, failures, and important events through email notifications and integrations.
Notification Types
Test Result Notifications
Test Execution Completed:
- When any test finishes
- Pass or fail status
- Execution duration
- Link to results
Test Execution Failed:
- Only when tests fail
- Error details
- Screenshots
- Troubleshooting hints
Recommended: Enable for critical tests only to avoid notification fatigue.
Discovery Notifications
Discovery Session Completed:
- When crawl finishes
- Pages discovered count
- Flows detected
- Patterns identified
Discovery Comparison Ready:
- When baseline comparison completes
- Change summary
- Critical issues detected
Test Plan Notifications
Test Plan Completed:
- When batch execution finishes
- Overall pass/fail summary
- Individual test status
- Execution duration
Test Plan Failed:
- When any test in plan fails
- Which tests failed
- Quick access to failures
First Failure:
- Stop immediately after first failure
- Useful for smoke tests
Team Notifications
Member Invited:
- When new member joins
- Their role
- Who invited them
Member Removed:
- When member leaves
- Who removed them
Role Changed:
- Permission updates
- New responsibilities
Quota Notifications
Approaching Quota Limit:
- At 80% of quota
- At 90% of quota
- At 100% (limit reached)
Quota Reset:
- When monthly quota resets
- New limits available
Billing Notifications
Payment Success:
- Successful charges
- Invoice ready
- Next billing date
Payment Failed:
- Failed payment attempt
- Update payment method reminder
- Days until service interruption
Trial Ending:
- 7 days before trial ends
- 3 days before trial ends
- Trial ended
Delivery Channels
Email Notifications
Configure per user:
- Go to Settings → Notifications
- Toggle email notifications
- Select notification types
- Choose frequency:
- Instant
- Hourly digest
- Daily digest
Email includes:
- Clear subject line
- Summary of event
- Direct action links
- Unsubscribe option
In-App Notifications
Always enabled:
- Bell icon shows unread count
- Click to view notifications
- Mark as read/unread
- Clear all option
Notification center shows:
- Recent notifications (last 30 days)
- Filtered by type
- Quick actions available
Integration Notifications
Route notifications through:
- Slack - Team channels
- Microsoft Teams - Team channels
- Jira - Create issues automatically
- Trello - Create cards
- Webhooks - Custom endpoints
Best Practice: Use email for personal notifications, integrations for team notifications. This keeps individual inboxes cleaner.
Configuration
Global Notification Settings
Organization-wide defaults:
- Go to Organization Settings → Notifications
- Set default preferences
- All new members inherit these
Defaults apply to:
- New team members
- New projects
- New test plans
Project-Level Notifications
Override for specific projects:
- Go to Project Settings → Notifications
- Enable project-specific settings
- Configure as needed
Use cases:
- Critical projects need more alerts
- Side projects need fewer
- Different teams, different preferences
Personal Notification Preferences
Individual customization:
- Go to User Settings → Notifications
- Override organization defaults
- Set your own preferences
Respect team norms:
- Don’t miss critical alerts
- Balance staying informed vs inbox overload
Notification Filters
By Priority
Control which test priorities trigger notifications:
- Critical only - Only P0 tests
- Critical + High - P0 and P1 tests
- All priorities - Every test
By Tag
Filter by test tags:
- Include tags: Only tests with specific tags
- Exclude tags: Never notify for certain tags
Examples:
- Only notify for “smoke” tag tests
- Exclude “wip” (work-in-progress) tests
By Status
Choose which statuses notify:
- Failures only (recommended)
- All results (can be noisy)
- First failure only (for smoke tests)
By Time
Schedule quiet hours:
- Pause notifications during off-hours
- Set business hours only
- Configure timezone
Example: No notifications 10 PM - 8 AM
Frequency Options
Instant
Receive notifications immediately:
- Best for: Critical failures
- Use case: Need immediate attention
- Downside: Can be disruptive
Hourly Digest
Batched every hour:
- Best for: Regular monitoring
- Use case: Stay informed without constant alerts
- Recommended for: Test results, executions
Daily Digest
Once per day summary:
- Best for: Non-urgent updates
- Use case: Morning review of yesterday’s activity
- Recommended for: Analytics, reports, team activity
Delivery time: Configurable (default 8 AM)
Notification Management
Mark as Read
Keep notification center tidy:
- Click notification to mark read
- “Mark all as read” button
- Auto-mark after 30 days
Mute Notifications
Temporarily disable:
- Mute specific project
- Mute specific test
- Mute for time period (1 hour, 1 day, 1 week)
Use case: During development when tests are intentionally failing
Unsubscribe
Stop receiving specific notifications:
- Click unsubscribe in email
- Or disable in Settings → Notifications
- Can re-enable anytime
Smart Notifications
Intelligent Routing
BugBrain automatically:
- Routes to test creator for failures
- Notifies assigned team members
- Escalates recurring failures
- Reduces noise from flaky tests
Failure Grouping
Multiple failures grouped:
- Same error → One notification
- Multiple tests → Summary email
- Avoid spam from test plan failures
Priority-Based Delivery
Critical notifications:
- Sent immediately
- Multiple channels (email + Slack)
- Clear action required
Low priority:
- Batched in digest
- Single channel
- Informational only
Do Not Disturb
Enable DND mode:
- Go to Settings → Notifications
- Enable “Do Not Disturb”
- Set schedule (optional)
While DND is active:
- No email notifications
- No push notifications
- In-app notifications still appear
- Critical alerts still sent (configurable)
Notification Templates
Customize email templates: (Pro plan feature)
- Go to Settings → Notifications → Templates
- Select template to customize
- Edit subject and body
- Use variables:
{{testName}},{{status}}, etc. - Preview and save
Use case: Match your team’s communication style
Analytics
Track notification effectiveness:
- Go to Settings → Notifications → Analytics
- View metrics:
- Delivery rate
- Open rate
- Click-through rate
- Unsubscribe rate
Optimize based on data:
- High unsubscribe = too many notifications
- Low open rate = wrong timing or irrelevant
- High click rate = notifications are valuable
Best Practices
1. Start Minimal Enable only critical notifications initially, add more as needed
2. Use Appropriate Channels Personal issues → Email, Team issues → Slack/Teams
3. Respect Timezones Configure quiet hours based on team timezones
4. Filter Aggressively Only notify on tests that matter
5. Review Regularly Monthly review of what’s working, disable unused notifications
6. Test Your Setup Use test notification feature to verify delivery
Troubleshooting
Not receiving emails?
- Check spam/junk folder
- Verify email address correct
- Check email notifications enabled
- Add noreply@bugbrain.tech to contacts
Too many notifications?
- Switch to digest mode
- Filter by priority or tags
- Mute non-critical projects
- Use Do Not Disturb mode
Notifications delayed?
- Check if using digest mode
- Verify timezone settings
- Check email server delays
- Contact support if persistent
Integration not working?
- Verify integration is configured
- Test integration connection
- Check event filters
- Review integration logs
Next Steps
- Set up Slack integration for team notifications
- Configure Jira integration for issue tracking
- Create test plans with smart notifications
- Customize notification preferences