# Test notifications

> The ways Semaloop can tell you a test run finished — Slack, GitHub pull request checks, and webhooks.

Rendered version: https://docs.semaloop.com/test-results/notifications/

The easiest way to get notified when your test suite has been executed is by using our [Slack integration](/integrations/slack/). Our Slack notifications have two purposes:

* A full build summary notification shared to a channel in your workspace
* An individual notification when you subscribe to a test run

Our full build summary ensures that we automatically tell you what’s broken with a Slack message whenever you ship a new build. And, if for some reason you update the test spec to try and fix a failing test, a build notification updates in place, rather than posting a new message or leaving you with out-of-date context.

Note

Manual reruns do not trigger the test suite channel summary message, as this is only generated after an automatic run.

If you’re pushing builds to Semaloop through the [Semaloop CLI](/integrations/cli/), and choose to enable our [GitHub integration](/integrations/github/), we can also report the status of your test runs as checks on your GitHub PR.

To notify something other than a person — a ticket tracker, a pager, a coding agent — use [webhooks](/integrations/webhooks/). Semaloop posts a signed `test_run.status_changed.v1` event to your endpoint as each run reaches `success`, `failure` or `error`.

## Related

- Index of every Semaloop docs page: https://docs.semaloop.com/llms.txt
- All Semaloop docs in one file: https://docs.semaloop.com/llms-full.txt
