Sf Testing
Skill Verified ActiveApex test execution, coverage analysis, and test-fix loops with 120-point scoring. TRIGGER when: user runs Apex tests, checks code coverage, fixes failing tests, or touches *Test.cls / *_Test.cls files. DO NOT TRIGGER when: writing Apex production code (use sf-apex), Agentforce agent testing (use sf-ai-agentforce-testing), or Jest/LWC tests (use sf-lwc).
To enable developers to efficiently execute Apex tests, analyze coverage, and automate the process of fixing failing tests and improving code quality.
Features
- Execute Apex tests with detailed reporting
- Analyze code coverage and identify gaps
- Automate test-fix loops for failing tests
- Provide guidance on Apex testing best practices
- Score tests against production-grade criteria
Use Cases
- When running Apex unit tests and encountering failures
- When needing to check code coverage for Apex classes
- When improving the quality and reliability of Apex test suites
- When aiming for higher Apex test coverage thresholds before deployment
Non-Goals
- Writing or refactoring Apex production code (use sf-apex)
- Testing Agentforce agents (use sf-ai-agentforce-testing)
- Testing LWC with Jest (use sf-lwc)
Workflow
- Discover test scope
- Run the smallest useful test set
- Analyze results
- Run a disciplined fix loop
- Improve coverage intentionally
Practices
- Test execution
- Coverage analysis
- Test-fix loop
- Testing best practices
Prerequisites
- sf CLI v2
- Target Salesforce org
- Test classes in org or local project
Installation
npx skills add jaganpro/sf-skillsRuns the Vercel skills CLI (skills.sh) via npx — needs Node.js locally and at least one installed skills-compatible agent (Claude Code, Cursor, Codex, …). Assumes the repo follows the agentskills.io format.
Quality Score
VerifiedSimilar Extensions
Salesforce Developer
100Writes and debugs Apex code, builds Lightning Web Components, optimizes SOQL queries, implements triggers, batch jobs, platform events, and integrations on the Salesforce platform. Use when developing Salesforce applications, customizing CRM workflows, managing governor limits, bulk processing, or setting up Salesforce DX and CI/CD pipelines.
Openclaw Testing
100Choose, run, rerun, or debug OpenClaw tests, CI checks, Docker E2E lanes, release validation, and the cheapest safe verification path.
Crabbox
100Use Crabbox for OpenClaw remote validation across Linux, macOS, Windows, and WSL2. Default to Blacksmith Testbox for broad Linux proof; includes direct Blacksmith and owned AWS/Hetzner fallback notes when Crabbox fails.
Sf Data
99Salesforce data operations with 130-point scoring. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, or needs data factory patterns for Apex tests. DO NOT TRIGGER when: SOQL query writing only (use sf-soql), Apex test execution (use sf-testing), or metadata deployment (use sf-deploy).
Sf Integration
98Salesforce integration architecture with 120-point scoring. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use sf-connected-apps), Apex-only logic (use sf-apex), or data import/export (use sf-data).
Sf Industry Commoncore Callable Apex
98Salesforce Industries Common Core (OmniStudio/Vlocity) Apex callable generation and review with 120-point scoring. TRIGGER when: user creates or reviews System.Callable classes, migrates `VlocityOpenInterface` / `VlocityOpenInterface2`, or builds Industries callable extensions used by OmniStudio, Integration Procedures, or DataRaptors. DO NOT TRIGGER when: generic Apex classes/triggers (use sf-apex), building Integration Procedures (use sf-industry-commoncore-integration-procedure), authoring OmniScripts (use sf-industry-commoncore-omniscript), configuring Data Mappers (use sf-industry-commoncore-datamapper), or analyzing namespace/dependency issues (use sf-industry-commoncore-omnistudio-analyze).