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

Running Apex Tests

  • 485 installs
  • 787 repo stars
  • Updated August 5, 2026
  • forcedotcom/afv-library

This is a copy of running-apex-tests by forcedotcom - installs and ranking accrue to the original listing.

running-apex-tests is a Claude Code skill that runs Salesforce Apex tests, analyzes code coverage with 120-point scoring, and drives test-fix loops for developers working on *Test.cls files.

About

running-apex-tests is an agent skill that executes Salesforce Apex tests, analyzes code coverage, interprets test failures, and guides developers through systematic test-fix loops. It activates automatically when the user runs Apex tests, checks coverage metrics, works with *Test.cls or *_Test.cls files, or needs to improve test quality. The skill gathers required context such as target org alias and test scope, then runs tests, scores results on a 120-point scale, highlights gaps, and iterates until the codebase meets coverage and quality standards. It is designed specifically for Apex unit testing inside Salesforce projects and does not overlap with production code generation, Agentforce agent testing, or LWC/Jest testing.

  • Executes sf apex run test workflows with full result parsing
  • Delivers 120-point scoring system for coverage and quality assessment
  • Identifies uncovered lines and suggests missing test scenarios
  • Manages structured test-fix loops until coverage and quality targets are met
  • Clearly distinguishes from production code generation and other test types

Running Apex Tests by the numbers

  • 485 all-time installs (skills.sh)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/forcedotcom/afv-library --skill running-apex-tests

Add your badge

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

Listed on Skillselion
Installs485
repo stars787
Last updatedAugust 5, 2026
Repositoryforcedotcom/afv-library

How do you run Apex tests and check coverage?

Run Apex tests, analyze code coverage, diagnose failures, and maintain a disciplined test-fix loop for Salesforce development.

Who is it for?

Salesforce developers validating Apex deployments who need coverage analysis and structured test-fix iteration.

Skip if: Lightning Web Component Jest tests, Agentforce agent testing, or writing new production Apex without executing tests.

When should I use this skill?

A developer runs Apex tests, checks code coverage, fixes failing *Test.cls files, or touches Salesforce test classes.

What you get

Apex test run results, coverage report with 120-point score, and diagnosed fixes for failing *Test.cls cases.

  • Test execution report
  • Coverage score and failure diagnosis

By the numbers

  • Uses 120-point scoring for Apex test coverage analysis
  • Skill version 1.1 in forcedotcom/afv-library

Files

SKILL.mdMarkdownGitHub ↗

running-apex-tests: 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 running-apex-tests 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 → generating-apex skill
  • testing Agentforce agents → testing-agentforce skill
  • testing LWC with Jest → generating-lwc-components

---

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 generating-apex skill 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

RuleRationale
Default to SeeAllData=falseEnsures test isolation; prevents reliance on org-specific data
Every test must assert meaningful outcomesTests with no assertions prove nothing and give false confidence
Test bulk behavior with 251+ recordsTriggers process in batches of 200; 251 records crosses the boundary
Use factories / @TestSetup when they improve clarityConsistent data creation in one place; rolled back between test methods
Pair Test.startTest() with Test.stopTest() for asyncEnsures async operations (queueable, future) complete before assertions
Do not hide flaky org dependencies inside testsPrevents intermittent failures tied to org state

---

Gotchas

IssueResolution
Test passes locally but fails in CI orgCheck for SeeAllData=true or undeclared dependencies on org-specific records
Coverage drops unexpectedly after refactorRun focused class-level tests first, then widen to RunLocalTests to confirm
"Uncommitted work pending" error in callout testDML and HTTP callouts cannot be mixed in the same test context without Test.startTest() wrapping
Mock not taking effect in testEnsure Test.setMock() is called before the code that makes the callout
@TestSetup data missing in test method@TestSetup data is committed per test method — re-query it; do not store in static variables

---

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 test classesgenerating-apex skillCode generation and repair
Create bulk / edge-case test datahandling-sf-dataRealistic test datasets
Deploy updated tests to orgdeploying-metadataDeployment workflows
Inspect detailed runtime logsdebugging-apex-logsDeeper failure analysis

---

Reference File Index

FileWhen to read
references/cli-commands.mdAll sf apex run test command flags, output formats, async execution, and coverage commands
references/test-patterns.mdTest class templates — basic, bulk (251+), mock callout, and data factory patterns
references/testing-best-practices.mdCore testing principles — AAA pattern, naming conventions, bulk, negative, and mock strategies
references/test-fix-loop.mdAgentic test-fix loop implementation and failure analysis decision tree
references/mocking-patterns.mdHttpCalloutMock, DML mocking, StubProvider, and selector mocking patterns
references/performance-optimization.mdTechniques to reduce test execution time — DML mocking, SOQL mocking, loop optimizations
assets/basic-test.clsTemplate: standard test class with @TestSetup, positive / negative / bulk / edge-case methods
assets/bulk-test.clsTemplate: bulk test with 251+ records that crosses the 200-record trigger batch boundary
assets/mock-callout-test.clsTemplate: HTTP callout mock using HttpCalloutMock
assets/test-data-factory.clsTemplate: reusable TestDataFactory with create and insert helpers
assets/dml-mock.clsTemplate: IDML interface + DMLMock implementation for database-free unit tests
assets/stub-provider-example.clsTemplate: StubProvider-based dependency injection stub
hooks/scripts/parse-test-results.pyPost-tool hook — parses sf apex run test JSON output and formats failures for the auto-fix loop

---

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

How it compares

Use running-apex-tests for Apex and coverage gates; switch to generating-lwc-components skills for Jest-based Lightning tests.

FAQ

What files trigger running-apex-tests?

running-apex-tests triggers on Apex test execution, coverage checks, and edits to *Test.cls or *_Test.cls files. It does not handle LWC Jest tests or Agentforce agent testing.

What scoring does running-apex-tests use for coverage?

running-apex-tests applies a 120-point scoring rubric during Apex test execution and coverage analysis at skill version 1.1, guiding disciplined test-fix loops before deployment.

This week in AI coding

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

unsubscribe anytime.