sf-testinglisted

<!-- Adapted from Jaganpro/sf-skills@ff1ab74 (MIT). This file layers Brite conventions from brite-salesforce/CLAUDE.md §Apex & Automation (lines 175-196) + §Engineering Standards (line 42). --> # sf-testing: Salesforce Test Execution & Coverage Analysis (Brite edition) 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. ## Brite Context Brite's test stance: - **Coverage target is 100% per class, not the SF 75% floor.** 90%+ org-wide is the target. Required for all triggers and service classes. Source: `brite-salesforce/CLAUDE.md` §Engineering Standards line 42. - **Apex-first Brite code requires Apex tests.** Flows are limited to screen flows and simple notifications (sf-flow covers the policy); everything else is Apex, so trigger tests, service tests, and bulk-path coverage are non-negotiable. - **LWC Jest runs at pre-commit.** The pre-commit hook executes Jest tests for staged LWCs; any new LWC ships with Jest coverage. - **Escape-hatch discipline.** `@TestVisible` + `Test.isRunningTest()` gate narrow exceptions (e.g., `Bypass_Validation_Rules` honoring on security-critical paths); the pattern is narrow-scoped per check, never a blanket sibling bypass. **See also:** [sf-apex](../sf-apex/SKILL.md) for production Apex patterns (trigger handler dispatch, Queueable `BATCH_SIZE=90` self-chaining, `Bypass_Val