forcedotcom/sf-skills

dx-devops-test-suite-assignments-configure

Recommends and manages DevOps Center test suite assignments for pipeline stages.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/forcedotcom/sf-skills --skill dx-devops-test-suite-assignments-configure

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Configure DevOps Center Suite Assignments

Recommends which existing test suites to run for a change, and manages how suites are assigned and mapped to pipeline stages. These operations share the same suite-stage metadata: a recommendation surfaces relevant suites and flags gaps, and those gaps lead directly into assignment.

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

Important: All DevOps Center data lives in the Salesforce org — NOT the local repo. Never search the filesystem for suite configuration. Always query the org with sf data query or sf api request rest.


Step 1 — Run prerequisites first (always)

Run the prerequisite checks in references/prerequisite-checks.md before any query or system call. On any failure, surface the plain-language message and stop.

  • Mode A (recommend): Prerequisites 1–4 (org login, plugin, DevOps Center org auth, pipeline identified). No stage required — recommendation reads the pipeline-level Review trigger.
  • Modes B–D (assign/map/classes): Prerequisites 1–4 and Prerequisite 5 (stage). You need doce-org-alias, pipelineId, and stageId.

Step 2 — Select the mode

If the user wants to…ModeFollow
Know which suites to run for a commit/diff, or what covers their changesA — Recommend suitesreferences/recommendation-logic.md
Assign one suite to a stage as a one-offB — Assign a single suitereferences/suite-assignment-modes.md
Bulk-map multiple suites to a stage as a testing strategyC — Map multiple suitesreferences/suite-assignment-modes.md
Add/remove individual test classes within a suite assignmentD — Add/remove classesreferences/suite-assignment-modes.md

Mode A is pure reasoning (no writes). Modes B–D mutate org state via the same testSuiteStages endpoint (references/api-endpoint.md).

How A feeds B–D: When recommendation flags a relevant suite that is not assigned to the stage, that gap is the input to Mode B/C. When it flags a new method with no suite coverage, direct the developer to author tests manually (v1 constraint — never suggest generating tests here).


Step 3 — Governance & confirmation (Modes B–D)

Modes B–D must confirm before any write:

  • Mode B — single confirmation prompt naming the suite, stage, and event.
  • Mode C — a mandatory impact-preview table (Suite / Stage / Event / Action) before the confirmation gate.
  • Mode D — re-present the final test list before confirming. Rejected tests must be EXCLUDED from the payload. If tests were modified during review, re-present the final list before requesting confirmation. Never call without explicit approval.

Do not call the API until the user gives an affirmative response. If the user declines, stop without writing. Full wording for each gate is in references/suite-assignment-modes.md.

Mode A (recommendation) makes no writes and needs no confirmation gate.


Step 4 — Execute and report

Follow the chosen reference file:

  • references/recommendation-logic.md — Mode A: diff classification, provider matching, ranking, gap flagging, output format.
  • references/suite-assignment-modes.md — Modes B–D: inputs, confirmation wording, success messages.
  • references/api-endpoint.md — the shared testSuiteStages POST payload schema (Modes B–D).
  • references/error-handling.md — status-code → plain-language tables.

Never expose raw API errors, stack traces, or JSON to the user.


Related skills

  • `dx-devops-test-pipeline-configure` — if the suite you want to assign doesn't appear yet, configure or re-sync the provider; also configures quality gates on a stage after mapping.
  • `dx-devops-test-suite-run` — execute a recommended/assigned suite on a stage.
  • `dx-devops-test-failures-analyze` — analyze failures and improvement suggestions for the tests within a suite.

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
forcedotcom
커뮤니티

design-systems-slds-apply

Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons. Use when building any UI that needs SLDS, choosing between Lightning Base Components and SLDS Blueprints, applying styling hooks for theming, using utility classes for layout and spacing, or selecting icons. Triggers include \"build a modal\", \"create a form\", \"data table\", \"SLDS styling\", \"style with hooks\", \"add an icon\".

1시간 설치 수
1
GitHub Stars
1.2천
업데이트
11월 13일
forcedotcom
커뮤니티

dx-code-analyzer-run

Run Salesforce Code Analyzer to scan code for security, performance, best practice, and code style violations. Supports all engines (PMD, ESLint, CPD, RetireJS, Flow, SFGE, ApexGuru), targets (files, folders, git diff), categories, and severities. Also handles post-scan exploration: filtering results by engine/severity/category/file, and explaining what rules mean. TRIGGER when: user says 'scan my code', 'check security issues', 'run PMD/ESLint', 'find duplicates', 'analyze Flows', 'check vulner

1시간 설치 수
1
GitHub Stars
1.2천
업데이트
11월 13일
forcedotcom
커뮤니티

experience-lwc-accessibility-jest-run

Use ALWAYS when running Sa11y accessibility Jest tests for an LWC — locally before pushing, producing the command(s), running one file vs a suite, selecting tests by naming convention, saving Sa11y-rendered HTML, or reproducing a Sa11y/A11yBug failure. Covers core (Bazel; bazel test // : ) and standalone npx jest (.accessibility.test.js, @sa11y/jest). REQUIRED for a run-plan.md, a failing a11y test's exit code, or SA11Y/A11yBug/core-Bazel test paths. DO NOT TRIGGER for functional Jest tests, a11

1시간 설치 수
1
GitHub Stars
1.2천
업데이트
11월 13일
forcedotcom
커뮤니티

experience-lwc-generate

Lightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc//.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use platform-apex-generate), Aura components, or Visualforce.

1시간 설치 수
1
GitHub Stars
1.2천
업데이트
11월 13일