forcedotcom/sf-skills / plugins/builder/dx-devops/skills/dx-devops-test-suite-assignments-configure
dx-devops-test-suite-assignments-configure
VerifiedRecommends and manages DevOps Center test suite assignments for pipeline stages. Mode A analyzes a commit diff against assigned suite metadata to recommend relevant existing suites and flag coverage gaps (pure reasoning). Modes B-D assign a single suite, bulk-map multiple suites with a mandatory impact preview, or add/remove test classes with governance rules, via the testSuiteStages Connect API. Use this skill to recommend suites for a commit, assign or map suites to stages, or add/remove tests in a suite. TRIGGER when: the user asks which suites to run for a commit/diff or what covers their changes; a suite is unlinked and the user wants it assigned; the user wants to configure suite-to-stage mappings, assign multiple suites, or add/remove/sync tests in a suite. DO NOT TRIGGER when: configuring or syncing a test provider (use dx-devops-test-pipeline-configure), running suites (use dx-devops-test-suite-run), or authoring/running tests directly (use platform-apex-test-generate or platform-apex-test-run).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.4 KB |
| references/api-endpoint.md | markdown | 1.2 KB |
| references/error-handling.md | markdown | 909 B |
| references/prerequisite-checks.md | markdown | 5.1 KB |
| references/recommendation-logic.md | markdown | 4.8 KB |
| references/suite-assignment-modes.md | markdown | 3.1 KB |
references/suite-assignment-modes.md
View on GitHub# Modes B–D — Assign / Map / Manage Suite Classes
All three modes use the same `testSuiteStages` endpoint (`references/api-endpoint.md`). They differ in scope and the confirmation pattern required.
## Prerequisites & shared inputs
Run Prerequisites 1–4 **and** Prerequisite 5 (stage). You need:
| Variable | Description |
|---|---|
| `doce-org-alias` | Prerequisite 1 |
| `pipelineId` | Prerequisite 4 (pipeline selection) |
| `stageId` | Prerequisite 5 (stage selection) |
| `event` | `Pre-Promote`, `Post-Promote`, or `Review` |
---
## Mode B — Assign a single suite to a stage
Use when a relevant test suite already exists but is not yet linked to a stage and the user wants to add it as a single one-off assignment.
**Additional inputs:**
| Variable | Description |
|---|---|
| `testSuiteId` | ID of the suite to assign |
| `testSuiteName` | Name of the suite (for display in confirmation) |
**Confirmation gate (required before any API call):**
> "The suite `<testSuiteName>` is not currently assigned to the `<stageName>` stage (`<event>`). Would you like me to assign it now?"
Do not proceed until the user confirms.
**On success:**
> "Suite `<testSuiteName>` has been assigned to the `<stageName>` stage (`<event>`)."
---
## Mode C — Map multiple suites to a stage
Use when configuring suite-to-stage mappings across a pipeline or assigning multiple suites as part of a testing strategy.
**Additional inputs:**
| Input | Description |
|---|---|
| `testSuiteOperations` | List of `{testSuiteId, action: "add"\|"remove"}` |
**MANDATORY IMPACT PREVIEW — required before any changes.** Do not call the API until the user has confirmed the preview:
> "Here's the suite mapping I'll apply:
>
> | Suite | Stage | Event | Action |
> |---|---|---|---|
> | `<suiteName>` | `<stageName>` | `<event>` | Add |
> | `<suiteName2>` | `<stageName>` | `<event>` | Remove |
>
> Confirm to apply all changes?"
Only proceed after the user explicitly confirms.
**On success:**
> "Suite mapping applied. `<N>` suite(s) updated for the `<stageName>` stage."
---
## Mode D — Add/remove test classes in a suite
Use when the user wants to add or remove individual test classes within an existing suite assignment, sync reviewed tests into a suite, or promote tests to a suite.
**Additional inputs:**
| Input | Source |
|---|---|
| `testSuiteOperations` | List of `{testSuiteId, action: "add"\|"remove"}` |
**Governance rules:**
- **Never call this without explicit approval.** AI-reviewed or modified tests must be re-presented to the user before this call is made.
- Rejected tests must be EXCLUDED from the payload — do not include them even if they were previously in the suite.
- If tests were modified during review, re-present the final list before requesting confirmation.
**Confirmation gate (required — do not skip):**
> "I'm about to sync the following changes to the test suite:
> - **Add:** `<testSuiteName1>`, `<testSuiteName2>`
> - **Remove:** `<testSuiteName3>`
> - Stage: `<stageName>` | Event: `<event>`
>
> Confirm?"
Only proceed after explicit confirmation.
**On success:**
> "Test suite updated successfully for the `<stageName>` stage."
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |