dx-devops-test-pipeline-configure

forcedotcom/sf-skills

Configure DevOps Center pipeline testing: enable providers, sync suites, or set quality gates.

What is dx-devops-test-pipeline-configure?

Configures Salesforce DevOps Center pipeline testing infrastructure by enabling test providers, re-syncing provider suite lists, or creating quality gates with coverage rules on pipeline stages. Use this skill when setting up or refreshing test providers or defining quality thresholds for a pipeline stage.

Enable and configure test providers so their test suites become available in a pipeline
Re-sync configured providers to pull in new or updated test suites
Create and configure quality gates with coverage thresholds and testing benchmarks on pipeline stages
Route configuration requests across three distinct modes based on user intent
Enforce prerequisite checks and confirmation gates before any org mutations

How to install dx-devops-test-pipeline-configure

npx skills add https://github.com/forcedotcom/sf-skills --skill dx-devops-test-pipeline-configure

Prerequisites

Salesforce CLI (sf) version 2.67.0 or later
Agentforce DX plugin installed
Authenticated connection to a DevOps Center-enabled org
An existing DevOps Center pipeline identified
For quality gate configuration: a target pipeline stage identified

Claude Code

Cursor

Windsurf

Cline

How to use dx-devops-test-pipeline-configure

1.Run prerequisite checks to verify org login, plugin installation, and pipeline access
2.Determine the configuration mode: enabling a new provider (Mode A), syncing an existing provider (Mode B), or setting a quality gate (Mode C)
3.Fetch the pipeline's test providers to confirm provider status (Available vs. Configured)
4.Review the confirmation gate and impact preview (for quality gates) before proceeding
5.Execute the appropriate API calls via the selected mode's reference workflow
6.Verify success and report the configuration results to the user

Use cases

Good for

Enable a new test provider in DevOps Center so QA teams can assign its suites to pipeline stages
Re-sync an existing provider after new test suites are added upstream to make them available for assignment
Set a code-coverage quality gate on a pipeline stage to enforce minimum coverage thresholds before deployment
Configure a quality gate with custom rules to block deployments that fail testing benchmarks
Update testing infrastructure when onboarding a new testing tool or provider to a pipeline

Who it's for

DevOps engineers configuring Salesforce CI/CD pipelines
Release managers setting up quality gates and testing requirements
QA leads enabling test providers and managing test suite availability
Developers working with DevOps Center pipeline infrastructure

dx-devops-test-pipeline-configure FAQ

When should I use Mode A (configure) vs. Mode B (sync)?

Use Mode A when the provider is Available (not yet configured). Use Mode B when the provider is already Configured but you need to pull in new or updated test suites. Check the provider status via GET .../testProviders?status=all to disambiguate.

What if users can't see test suites when assigning to a stage?

That is a stage-assignment gap, not a configuration gap. Redirect the user to the dx-devops-test-suite-assignments-configure skill instead of retrying configuration.

Can I configure the same provider twice?

No. Posting to the configure endpoint for an already-configured provider creates duplicate DevopsPipelineTestProvider records. Always check provider status first and use sync (Mode B) for existing providers.

Do I need to identify a stage for all modes?

No. Modes A and B (provider configure/sync) work at the pipeline level and do not require a stage. Mode C (quality gate) requires a target stage to be identified.

What API version does this skill use?

All DevOps testing system calls target Salesforce API v67.0 (minimum required). Ensure your org supports this version.

Full instructions (SKILL.md)

Source of truth, from forcedotcom/sf-skills.

name: dx-devops-test-pipeline-configure description: "Configures DevOps Center pipeline testing infrastructure: enables a test provider so its suites become available, re-syncs a configured provider to pull in new suites, or creates a quality gate with rules on a stage. Routes by intent across three modes after running shared prerequisite checks and an explicit confirmation gate. Use this skill when a user wants to set up, configure, enable, sync, or refresh a test provider, or set/configure a quality gate or coverage threshold on a DevOps Center pipeline stage. TRIGGER when: the user wants to configure/enable/add/set up a test provider, re-sync or refresh a provider's suite list, pull in new suites, or set/configure a quality gate, coverage threshold, or testing benchmark on a stage. DO NOT TRIGGER when: assigning existing suites to a stage (use dx-devops-test-suite-assignments-configure), running or retriggering a suite (use dx-devops-test-suite-run), or non-DevOps-Center work." metadata: version: "1.0" domains: ["Developer Experience"] minApiVersion: "67.0" relatedSkills: - "dx-devops-test-failures-analyze" - "dx-devops-test-suite-assignments-configure" - "dx-devops-test-suite-run" cliTools: - tool: ["sf"] semver: ">=2.67.0"

Configure DevOps Center Pipeline Testing Infrastructure

Sets up and configures a DevOps Center pipeline's testing infrastructure. This skill handles three closely related "configure your pipeline" operations that share the same org context, prerequisites, and entity scope (the pipeline level). Pick the mode that matches the user's intent.

API version: All DevOps testing system calls target Salesforce API v67.0 (minimum required).

Important: All DevOps Center data (pipelines, stages, providers, suites, gates) lives in the Salesforce org — NOT the local repo. Never search the filesystem for pipeline configuration. Always query the org with sf data query or sf api request rest.

Step 1 — Run prerequisites first (always)

Before any query or system call, run the prerequisite checks in references/prerequisite-checks.md. On any failure, surface the plain-language message and stop — never write to an unverified environment.

Modes A & B (provider configure/sync): run Prerequisites 1–4 (org login, Agentforce DX plugin, DevOps Center org auth, pipeline identified). Prerequisite 5 (stage) is not required — providers are configured at the pipeline level.
Mode C (quality gate): run Prerequisites 1–4 and Prerequisite 5 (stage). Prereq 5 gives the DevopsPipelineStage only — the target DevopsTestSuiteStage record Id is resolved separately in Mode C's Step 0 (trigger → suite-stage row).

Carry forward the resolved doce-org-alias, pipelineId, and (Mode C) stageId / testSuiteStageId.

Step 2 — Select the mode

If the user wants to…	Mode	Follow
Enable / set up / add a provider that is not yet configured	A — Configure a test provider	`references/configuring-test-provider.md`
Re-sync / refresh an already-configured provider to pull in new suites	B — Sync a configured provider	`references/syncing-test-providers.md`
Set / configure a quality gate, coverage threshold, or testing benchmark on a stage	C — Configure a quality gate	`references/configuring-quality-gate.md`

Disambiguating A vs B (the critical decision): First fetch the pipeline's providers (GET .../testProviders?status=all) — both modes start there. Then:

Provider is Available (not configured) → Mode A (configure).
Provider is Configured but suites are stale/missing → Mode B (sync).
Provider is Configured and the user can't see suites when assigning to a stage → this is a stage-assignment gap, not a configuration gap. Redirect to dx-devops-test-suite-assignments-configure.

Never POST to the configure endpoint for an already-configured provider — it creates duplicate DevopsPipelineTestProvider records. See references/gotchas.md.

Step 3 — Confirmation gate (required in every mode)

Every mode mutates org state and must show a confirmation gate before any write. Each mode's reference file contains its exact gate wording (Mode C additionally requires a mandatory impact preview before the gate). Do not call any write API until the user gives an affirmative response. If the user declines, stop without writing.

Step 4 — Execute and report

Follow the chosen reference file for the exact API calls, success messages, and error handling:

references/configuring-test-provider.md — Mode A
references/syncing-test-providers.md — Mode B
references/configuring-quality-gate.md — Mode C
references/error-handling.md — consolidated status-code → plain-language tables for all modes
references/gotchas.md — duplicate-provider trap, API-name differences, trigger-type rules

Never expose raw API errors, stack traces, or JSON payloads to the user — always translate to plain language.

Related skills

dx-devops-test-suite-assignments-configure — after configuring/syncing a provider, assign or map its suites to a stage; also recommends which suites to run for a commit.
dx-devops-test-suite-run — run a suite, or retrigger a quality gate after fixes meet the threshold.
dx-devops-test-failures-analyze — explain failures from a run and optionally create a fix work item.