Full run history
Every invocation logs against the same job history as your dashboard.
Test Where Work Happens.
Trigger jobs, rerun a single failing test, and get results back in the channel — right from the release conversation your team is already having.
# release-checks
live
M
Maya10:42
Shipping the auth fix — can we knock the integration suite out before standup?
/devassure run-job auth-integration
DA
DevAssure10:42
job auth-integrationrunning
How it works
Three steps, no context switch
Connect Slack
Configure Slack integration in the DevAssure web portal.
Run a command
Type /devassure run-job or the short alias /da and pick a job, or pass an id directly.
Watch results land
Pass, fail, and pending counts post back to the thread as the run completes.
Product demo
Built for slack channels
Run your tests without leaving Slack
Every command works in a DM or any channel in your workspace.
Fails loudly, on purpose
A failing run posts back with enough detail to act on immediately.
Works alongside CI
Keep your pipeline triggers as-is; Slack becomes an additional way in.
Zero-setup for the team
No local agent, browser, or CLI needed to trigger a run from Slack.
COMMANDS
Every command, right where you work
/devassure run-jobpick a job and run it/devassure run-job <id>run a job by id/devassure run-test <id>rerun a single test/dashort alias, same commandsRESULTS
Results post back automatically
Pass, fail, and pending counts land in the same thread the run was triggered from — visible to everyone already in the conversation.
- Posts back to the exact thread that started it
- Visible to the whole channel, not just the requester
- Links straight to the full report for details
Before and after
Stop pasting links to a dashboard
The run, its status, and the discussion about it live in the same thread.
Without Slack integration
- ✗Switch tabs to trigger a run
- ✗Paste dashboard links into chat
- ✗Ask 'is it done yet?' in the thread
- ✗Failures discovered late
With DevAssure for Slack
- ✓Run it with a slash command
- ✓Results post to the thread themselves
- ✓Status visible to the whole channel
- ✓Failures flagged the moment they happen
Your tests are one message away
Two-minute setup. No infrastructure to own. Just the commands your team already runs, from the channel they're already in.
Add to SlackFAQ
Questions about DevAssure for Slack
What teams ask before adding the app to a workspace.
Do I need to install anything besides the Slack app?
No. Connect Slack Workspace to DevAssure, authorize the workspace, and the commands are live — no local agent, browser, or CLI required to trigger a run.
Which channels can run tests?
All channels in your workspace. Scope it to a single #release-checks channel or open it up workspace-wide.
Does a run triggered from Slack show up in the dashboard?
Yes. Every /devassure run is logged against the same job history as runs triggered from the dashboard, your CI pipeline, or the CLI — one history, three ways in.
Can I rerun just one failing test instead of the whole suite?
Yes — /devassure run-test <test-id> reruns a single test and posts the result back to the same thread, so you're not waiting on the full suite to chase one failure.
What happens if a run fails?
The agent posts back with what failed and a link to the full report — enough to act on without leaving the channel to find out what broke.