Alerting on critical failures and testing insights in your workspace is critical to minimizing the impact of issues and regressions detected by your automated testing. To assist with this effort, mabl integrates with the tools your team uses to communicate and coordinate, including Microsoft Teams.
Plan information is sent to the selected channel as soon as it happens in mabl.
By configuring mabl to send notifications directly to a Teams channel of your choice, you can:
- Speed up the issue triage response time by setting alerts for critical failures
- Set filters to monitor mabl for the insights your team cares about the most, such as auto-heal, broken link, and visual change insights
- Keep up to date on comments in test output without having to log into the mabl app
This guide outlines how to set up and configure the Microsoft Teams integration.
Retirement of Office 365 Connectors
In July 2024, Microsoft announced that Office 365 Connectors will no longer be supported after 31 December 2025.
If you configured your mabl Microsoft Teams integration using Office 365 Connectors, you must migrate to using Microsoft's proposed Workflows Solution. Please see the Teams section of this document for instructions on configuring the mabl Microsoft Teams integration with Workflows.
Setup
To set up the Teams integration, you need to add a webhook URL in the Teams channel where you want to receive notifications. You'll use this webhook URL to finish setting up the integration in mabl.
In Teams
Microsoft recommends using Workflows to create incoming webhooks for specific MS Teams channels. If you don't have enough permissions to add a webhook, find someone on your team with the correct privileges.
To generate the HTTP POST URL required to set up the MS Teams integration, follow Microsoft's instructions on configuring incoming webhooks with Workflows. Copy the URL and finish setting up the integration in mabl.
In mabl
In the mabl app, navigate to Settings > Integration to finish setting up the Teams integration:
- Find the Microsoft Teams integration card and click on the + Setup button.
- On the Teams setup form, enter the following required information:
- Name: Name your integration something that you can easily identify, such as the name of the channel that it's sending data to.
- Webhook URL: Paste in the webhook URL that you copied from the Teams webhook configuration.
- Modify the Configuration options to suit your needs. For more details on configuration options, see the following section.
- Click Save.
A sample configuration that alerts on plan runs, comments, visual changes, and broken links
After saving, the integration appears in the Active integrations section of Settings > Integrations.
Teams integration on Settings > Integrations
Configuration
Use the toggles and filters to configure the Teams integration to fit your needs.
The basics:
- Action buttons in cards: If this option is toggled on, you can trigger failed plans to re-run directly from Teams.
Plan notifications
- Plan run passed
- Plan run failed: This option includes a note on the first error encountered during the plan run, who was the last user to modify the test, and when the test was updated.
- Plan run started
- Plan run status changed: This option sends notifications if a plan run passes after a previous failing run, or if a plan run fails after a previous passing run. If the status changes to failing, the notification includes details on the last user to modify the test and when the test was updated.
Other notifications
Configuration notifications for other types of insights:
- Comments: Comments added to the test output page.
- Application broken: Includes insights around home page load failures and auto-login failures.
- Timing: Page load and test execution timing insights.
- Broken links: URL for broken and fixed links
- Auto-heal: mabl adapts to find page elements in browser tests
- Visual changes: Insights about visual differences found during test runs. Enable visual change learning on your plans to receive these insights.
- JavaScript errors: New and fixed JavaScript errors encountered during test runs
- Integration events: Insights around integration events with mabl, such as new OAuth(Slack) integration added, first successful deployment, and first plan execution
Only notify for
Insight statuses
Place a filter on the notifications configured in the "Plan notifications" and "Other notifications" sections to surface specific types of insights.
For example, if you want to receive notifications only when a scheduled plan's status changes from passing to failing, toggle on Plan run status changed and set the Insight filter to "Alert." This configuration filters out Plan run passing insights and only notifies you when there is a Plan run failing insight.
If you want to know when a test has JavaScript errors, but you don't want to know the JavaScript errors are fixed, toggle on JavaScript errors and set the Insight filter to "Warning." This configuration filters out JavaScript fixed insights and only notifies you when there is a JavaScript broken insight.
Use the plan labels filter to receive notifications only for plans that have certain labels. When multiple labels are selected, you get a notification if a matching plan is tagged with any of the labels.