Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jaganpro avatar

Sf Testing

  • 1.4k installs
  • 423 repo stars
  • Updated April 27, 2026
  • jaganpro/sf-skills

sf-testing is an agent skill that apply sf-testing agent skill workflows from documented skill.md guidance.

About

sf-testing is an agent skill from jaganpro/sf-skills that apply sf-testing agent skill workflows from documented skill.md guidance. # sf-testing: Salesforce Test Execution & Coverage Analysis Use this skill when the user needs **Apex test execution and failure analysis**: running tests, checking coverage, interpreting failures, improving coverage, and managing a disciplined test-fix loop for Salesforce code. ## When This Skill Owns the Task Use `sf-testing` when the work inv Developers invoke sf-testing during ship/testing work for testing & qa tasks. The skill documents triggers, prerequisites, and step-by-step workflows grounded in SKILL.md. Compatible with Claude Code, Cursor, and Codex agent runtimes that load marketplace skills. Review the Security Audits panel on this listing before installing in production environments. Category Testing & QA with development vertical focus supports repeatable agent-guided delivery.

  • sf-testing: Salesforce Test Execution & Coverage Analysis
  • When This Skill Owns the Task
  • Use `sf-testing` when the work involves:
  • `sf apex run test` workflows
  • identifying uncovered lines and missing test scenarios

Sf Testing by the numbers

  • 1,360 all-time installs (skills.sh)
  • +4 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #498 of 2,153 Testing & QA skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
At a glance

sf-testing capabilities & compatibility

Capabilities
sf testing: salesforce test execution & coverage · when this skill owns the task · use `sf testing` when the work involves: · `sf apex run test` workflows · identifying uncovered lines and missing test sce
Use cases
orchestration
From the docs

What sf-testing says it does

- identifying uncovered lines and missing test scenarios
SKILL.md
- structured test-fix loops for Apex code
SKILL.md
- writing or refactoring production Apex → [sf-apex](../sf-apex/SKILL.md)
SKILL.md
npx skills add https://github.com/jaganpro/sf-skills --skill sf-testing

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1.4k
repo stars423
Security audit3 / 3 scanners passed
Last updatedApril 27, 2026
Repositoryjaganpro/sf-skills

What it does

Apply sf-testing agent skill workflows from documented SKILL.md guidance.

Who is it for?

Developers working on testing & qa during ship tasks.

Skip if: Tasks outside Testing & QA scope described in SKILL.md.

When should I use this skill?

Apply sf-testing agent skill workflows from documented SKILL.md guidance.

What you get

Completed testing & qa workflow aligned with SKILL.md steps.

  • Apex @IsTest .cls file
  • TestSetup data factory stubs

By the numbers

  • Targets 90%+ Apex code coverage in generated test class headers

Files

SKILL.mdMarkdownGitHub ↗

sf-testing: Salesforce Test Execution & Coverage Analysis

Use this skill when the user needs Apex test execution and failure analysis: running tests, checking coverage, interpreting failures, improving coverage, and managing a disciplined test-fix loop for Salesforce code.

When This Skill Owns the Task

Use sf-testing when the work involves:

  • sf apex run test workflows
  • Apex unit-test failures
  • code coverage analysis
  • identifying uncovered lines and missing test scenarios
  • structured test-fix loops for Apex code

Delegate elsewhere when the user is:

  • writing or refactoring production Apex → sf-apex
  • testing Agentforce agents → sf-ai-agentforce-testing
  • testing LWC with Jest → sf-lwc

---

Required Context to Gather First

Ask for or infer:

  • target org alias
  • desired test scope: single class, specific methods, suite, or local tests
  • coverage threshold expectation
  • whether the user wants diagnosis only or a test-fix loop
  • whether related test data factories already exist

---

Recommended Workflow

1. Discover test scope

Identify:

  • existing test classes
  • target production classes
  • test data factories / setup helpers

2. Run the smallest useful test set first

Start narrow when debugging a failure; widen only after the fix is stable.

3. Analyze results

Focus on:

  • failing methods
  • exception types and stack traces
  • uncovered lines / weak coverage areas
  • whether failures indicate bad test data, brittle assertions, or broken production logic

4. Run a disciplined fix loop

When the issue is code or test quality:

  • delegate code fixes to sf-apex when needed
  • add or improve tests
  • rerun focused tests before broader regression

5. Improve coverage intentionally

Cover:

  • positive path
  • negative / exception path
  • bulk path (251+ records where appropriate)
  • callout or async path when relevant

---

High-Signal Rules

  • default to SeeAllData=false
  • every test should assert meaningful outcomes
  • test bulk behavior, not just single-record happy paths
  • use factories / @TestSetup when they improve clarity and speed
  • pair Test.startTest() with Test.stopTest() when async behavior matters
  • do not hide flaky org dependencies inside tests

---

Output Format

When finishing, report in this order: 1. What tests were run 2. Pass/fail summary 3. Coverage result 4. Root-cause findings 5. Fix or next-run recommendation

Suggested shape:

Test run: <scope>
Org: <alias>
Result: <passed / partial / failed>
Coverage: <percent / key classes>
Issues: <highest-signal failures>
Next step: <fix class, add test, rerun scope, or widen regression>

---

Cross-Skill Integration

NeedDelegate toReason
fix production code or author testssf-apexcode generation and repair
create bulk / edge-case datasf-datarealistic test datasets
deploy updated testssf-deployrollout
inspect detailed runtime logssf-debugdeeper failure analysis

---

Reference Map

Start here

  • references/cli-commands.md
  • references/test-patterns.md
  • references/testing-best-practices.md
  • references/test-fix-loop.md

Specialized guidance

  • references/mocking-patterns.md
  • references/performance-optimization.md
  • assets/

---

Score Guide

ScoreMeaning
108+strong production-grade test confidence
96–107good test suite with minor gaps
84–95acceptable but strengthen coverage / assertions
< 84below standard; revise before relying on it

Related skills

Forks & variants (1)

Sf Testing has 1 known copy in the catalog totaling 34 installs. They canonicalize to this original listing.

How it compares

Choose sf-testing over generic unit-test generators when output must be valid Apex with @IsTest, bulk limits, and Salesforce deployment coverage rules.

FAQ

What does sf-testing do?

Apply sf-testing agent skill workflows from documented SKILL.md guidance.

When should I use sf-testing?

During ship testing work for testing & qa.

Is sf-testing safe to install?

Review the Security Audits panel on this listing before production use.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.