Apex test class generator
Generate production-ready Apex test classes — TestDataFactory patterns, bulk testing with 251+ records, mocking, exact assertions — with disciplined fix loops and coverage targets
- What
- Generate production-ready Apex test classes — TestDataFactory patterns, bulk testing with 251+ records, mocking, exact assertions — with disciplined fix loops and coverage targets
- Cost
- Free
- Needs
- a Salesforce org (authenticate with `sf org login web --alias <alias>`) to run tests against; the sf CLI (>=2.0.0); an Apex codebase with production classes to test
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @forcedotcom's discipline for generating production-ready Apex test classes: one behavior per test method (never combine null and empty in one method), bulk tests with 251+ records to cross the 200-record trigger batch boundary, every `@TestSetup` delegating to a `TestDataFactory` (never inline lists, never org data, never hardcoded IDs), exact expected values in assertions with failure messages, the `Assert` class only (never legacy `System.assert`), mocked external boundaries (`HttpCalloutMock`, `Test.setFixedSearchResults`, DML mocks), negative paths and exception scenarios, `Test.startTest()`/`Test.stopTest()` wraps, and a fix loop capped at 3 iterations — stop and surface the root cause if still failing. Coverage targets: 75% minimum for deploy, 90%+ recommended, 100% on critical paths. By @forcedotcom, listed here with credit to its creator. Honest caveats: requires the sf CLI authenticated against an org to run tests; covers triggers, services, controllers, batch, queueable, callouts, selectors, scheduled jobs and platform events — but NOT production Apex (use the sibling `platform-apex-generate` skill) and NOT Jest/LWC tests; anti-pattern fixes (SOQL/DML in loops, magic numbers, god classes, generic catches) included. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a Salesforce org (authenticate with `sf org login web --alias <alias>`) to run tests against; the sf CLI (>=2.0.0); an Apex codebase with production classes to test Install "Apex test class generator" for me. It teaches the agent @forcedotcom's test-generation discipline: gather context (target classes, existing factories, coverage threshold), generate {ClassName}Test.cls plus its -meta.xml from the asset templates (creating TestDataFactory.cls first if none exists), then run the tests with `sf apex run test`, analyze failures and coverage, and loop fixes up to 3 iterations before surfacing root cause — with one-behavior-per-method tests, 251+ record bulk boundaries, Assert-only assertions, mocked callouts, and Given/When/Then structure. Repository: https://github.com/forcedotcom/sf-skills/blob/main/plugins/builder/salesforce-development/skills/platform-apex-test-generate/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "platform-apex-test-generate". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point it at the production class to test, confirm the org alias and coverage threshold — 75% deploy minimum, 90%+ recommended). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.