Skip to main content

Slack Integration

Run O2 jobs, filtered test sets, and single tests directly from Slack using the /devassure slash command (alias: /da). Results post back to the same channel as a score card — no dashboard tab required.

PrerequisitesDirect link to Prerequisites

  • A DevAssure account with Integrations access.
  • Permission to install apps in the target Slack workspace, or an existing Slack admin who can approve the install.
  • At least one saved job or test case in DevAssure, if you intend to run run-job or run-test immediately after setup.

SetupDirect link to Setup

  1. In the DevAssure app, go to Settings->Integrations.
  2. Select Slack and authorize your workspace when prompted by Slack's OAuth screen.
  3. Select Configure to view the connected workspace, set notification preferences, and see the command reference from within the app.

Once connected, /devassure and /da are available in all channel of your slack workspace, and in direct messages with the DevAssure agent.

CommandsDirect link to Commands

Type /devassure (or /da) and Slack surfaces the available subcommands as you type.

CommandDescription
/devassure or /devassure helpShow the command list
/devassure run-jobPick a job from a list and run it
/devassure run-job <job-id>Run a job by ID (JB-1 or just 1)
/devassure run or /devassure run-testsConfigure filters, then run matching tests
/devassure run-test <test-id>Run a single test (TC-1 or just 1)

/da is a full alias for /devassure — every command above works identically under either prefix.

Usage patternsDirect link to Usage patterns

Run a saved job by ID — the release-call path:

/da run-job 1

Run a single test — for a bug just reported in the channel:

/da run-test TC-42

Run a filtered set — for anything in between a single test and a full saved job (e.g. a smoke tag, a folder), use run or run-tests without arguments to open the filter configuration flow:

/da run

Result cardsDirect link to Result cards

When a triggered run finishes, DevAssure posts a summary card back to the channel it was triggered from. The card includes:

FieldDescription
HeaderJob name, who triggered the run, project, agent count, start time, and session ID
ScoreOverall score for the run
ScenariosScenarios completed out of total
ValidationsPassed and failed validation counts
ActionsActions the agent performed in the browser
DurationTotal run time
View Test SessionLink that opens the full session in DevAssure

A fully passing run requires no further action — the green card itself is the signal. A run with failures is one click away from the full session, including step-level evidence, via View Test Session.