Slack
Get run results and issues in each project's Slack channel, and ask Autonomy questions or start runs from Slack.
Slack does two things in Autonomy. It's where run results and new issues are posted, and it's a place to talk to Autonomy: ask what failed, look at issues, or start a run. Connect it once for the organization and both work.
Connect Slack
Owners and admins only.
- Open Organization → Integrations → Slack and click Connect. The setup has three steps: Sign in to Slack, Choose what to share, Use it in projects.
- Sign in and allow the Autonomy app in your Slack workspace.
- Choose the channels Autonomy may post to.
- Choose each project's channel. A project with no channel of its own uses the Default channel.
Autonomy posts to the channels you choose and never reads channel history.
Where messages go
| Setting | Where | What it gets |
|---|---|---|
| Default channel | Organization → Integrations → Slack | Every organization event, the events of projects without their own channel, and every Run failed. |
| A project's channel | Organization → Integrations → Slack, or Route by project on Organization → Notifications | That project's events. |
Run failed goes to the project's channel and to the default channel. When they're the same channel, it's posted once. Use Send test next to the default channel to check that Autonomy can post there.
Which events are sent at all is set on Organization → Notifications, and each member chooses what reaches them on My notifications. See Notifications and webhooks.
A message carries the test case, the environment, the result and a link to the run, not a copy of the run page. Start with failures and new issues for each project's team. Add passing results only to a channel that exists for release checks.
Talk to Autonomy
Mention @Autonomy in a channel, send it a direct message, open its App Home tab, or use it from the Slack assistant pane. Ask in plain words:
@Autonomy show me the most recent failed runs and what broke
@Autonomy what happened in step 3 of run_123?
@Autonomy list the open issues in this project
@Autonomy start a run of the checkout test case on staging
@Autonomy cancel run_789
@Autonomy mark issue_456 as resolvedWhat it can do:
| Area | It can |
|---|---|
| Projects | List the organization's projects. |
| Environments | List a project's environments. |
| Test cases | List and search test cases, and show a test case's steps. |
| Runs | List recent runs, show a run's result and each step's result, and show the Step Actions the agent took. |
| Start and cancel | Start a run of one test case in an environment, and cancel a queued or running run. |
| Issues | List issues, file a Bug or Risk, comment on an issue, and mark it resolved, ignored or open again. |
It gives results in words: Passed, Failed, Couldn't start, Cancelled. Changing an issue's status never changes a run's result.
In a project's channel, it works in that project unless you name another. Elsewhere, it asks which project you mean when that's unclear. It starts, cancels, files or changes something only when you ask, and only when the target is clear. Every request stays inside the organization the Slack workspace is connected to.
The assistant pane suggests four prompts to start with: Recent failures, Open issues, Test cases and Start a run. The App Home tab shows recent runs.
Troubleshooting
Messages arrive, but mentions are ignored
The Slack app was installed before Autonomy could answer in Slack, so it only has permission to post. An admin reconnects Slack in Organization → Integrations → Slack to grant the rest. Messages keep arriving meanwhile.
Slack shows as disconnected
Slack removed the app or revoked its access. An admin connects it again.
A project's messages go to the default channel
The project has no channel of its own. Choose one in Organization → Integrations → Slack or under Route by project.
It can't find a test case
Ask it to list test cases first, or give the exact name. It only matches test cases that exist, and won't guess.
It won't start a run
It needs one test case and an environment. Name both: "the checkout test case on staging". It starts test cases, not test plans.
Didn’t find it?