platform-apex-test-run

Run sf apex run test with --class-names for specific tests or --test-level RunLocalTests for all local tests, adding --code-coverage and --result-format json. Use --output-dir to save results and --target-org to specify the org alias.

Enable the agentic test-fix loop, which parses failure messages, classifies the error type such as NullPointerException or DmlException, suggests a root-cause fix, applies it, and re-runs the focused test. It iterates up to three attempts until tests pass.

Triggers process records in batches of 200, so 251 records crosses the batch boundary into a second chunk of 51. This reveals bulkification bugs like DML or SOQL inside loops that single-batch tests miss.

Implement the HttpCalloutMock interface with a respond method returning a fabricated HttpResponse, then register it with Test.setMock before invoking the code under test. Salesforce requires mocks because real callouts are blocked in tests.

DML and HTTP callouts cannot occur in the same transaction context. Wrap the callout code between Test.startTest and Test.stopTest so the DML commits before the mocked callout executes.

Use a different skill when writing production Apex code, testing Agentforce agents, or running Jest tests for Lightning Web Components. This skill covers only server-side Apex test execution, coverage, and failure analysis.