Testlio for Slack streamlines the communication of different events happening in the Testlio platform. Events can be sent to one or more Slack workspaces and multiple Testlio workspaces can send notifications to a single Slack channel. It's all up to you to decide which events to send and where. Read more about the setup process.

Available events

Various events can happen in the Testlio platform and you can subscribe to all events or each event independently.

Test Run Finished

Any time a run finishes, get notified that testing is done and issues have been reported. It's time to go and check what issues were found. You can choose to get notifications after all runs or only after manual or automated runs.

The notification includes:

Basic information about the results (how many tests were executed, pass rates, how many issues were found, how many devices were used)
A direct link to the run on the Testlio platform

Testlio for Slack - Run Finished event example

Integration: Syncing Error

Get notified when your Testlio issue management integration has problems with individual issues. The problems can vary based on the setup and restrictions in the integrated system. Potential problems include:

Errors creating issues (required fields not included in the integration, the integration doesn't have permission to create issues)
Errors changing an issue's state (the issue in your system is in a state not mapped into Testlio or in a different project than mapped into Testlio)
Another related to updating content (for example, the issues is closed and so the integration can't add a comment, the issue requires a field to be completed before it's closed)

The notification includes:

A link to the integration in the Testlio platform
A link to the issue in the Testlio platform and/or to the issue in your system (depending on factors such as the issue state)
A technical error message
A technical resource ID

An example sync error notification stating that the integration failed to send issue #414125 to Jira because "Cant move remote issue to state 'open'." and a resource ID.

Integration: Polling Error

Get notified when your Testlio issue management integration has a problem, either global (when all integrations are affected) or specific to your integration. The most common errors are:

The provided credentials are not valid.
The project/workspace in your system is no longer available (either the integration user has been removed or the project/workspace has been deleted).
Another technical error in your system.

The notification includes:

A link to the integration in the Testlio platform
A technical error message

An example polling error notification stating that polling changes failed and the message "Request to Jira failed with message: '404 No project could be found with id '1153700000'.'

Issues: Escaped or High Severity Issue Created

Get notified about events related to issues. After saving a configuration that includes Issue, the integration lists the included events and Issue has a pencil button to edit the specific issue events to include.

A Slack integration listing with the Slack Workspace, Channel, and selected Events. In the selected events next to Issue is a button to edit the issue settings.

You can choose to include the creation of escaped issues and/or high-priority issues. These let you get notifications of issues to start resolving without having to wait for the end of a run.

The notification includes:

The title of the issue
A link to the issue

An example high-priority issue notification stating that a new escaped issue was reported with the message "[Login] Button disabled with beta OS".

An example high-priority issue notification stating that a new high severity issue was created with the message "[Login] Can't log in on Safari".

Issues: Comment Mention

Get notifications whenever specific keywords (such as usernames or email addresses) are included in a comment on a synced issue. Configure the keywords for Jira or AzureDev Ops.

The notification includes:

The number and title of the issue
A link to the issue
The commenter’s username
The comment

Signal Created

Get notified whenever a new signal is created.

The notification includes:

A link to the signals in the Testlio platform
The date the signal was created
In a thread, the titles and IDs of the signals and where they came from

An example signal notification stating that new signals were created and two replies with signals for app reviews.

Insight Created

When your workspace has certain characteristics that are outside the norm for testing, LeoInsights generates insights to let you know so it can guide your testing strategy.

Insights are calculated daily, so notifications come at most once per day. Already reported insights do not generate new notifications.

The notification includes:

A description of the insight
Links to connected resources, usually reports showing the data behind the insight

A Slack notification with the text 'New insight detected' and linkes to the Tests and Runs reports.

Opportunity: Applicants and Status

Get updates when your work opportunities have status updates. Each opportunity within a workspace has its own thread that collects all updates on that opportunity.

Note that notifications are only sent for opportunities opened after the notification has been setup. Existing opportunities don’t send updates.

Potential updates include:

An opportunity is opened or reopened
An applicant was accepted
Spots changed
No applicants within 24h if the opportunity opening/reopening
No new applicants within 24h of the last acceptance
An applicant needs manual review
- In a manual opportunity
- In an automated opportunity (has a pay rate over the workspace max)
N applications pending review for manual opp.
Opportunity closed (such as automatically when all slots are filled)

The notification includes:

A description of the update
A link to the opportunity