platform-apex-test-generate

Generate Apex test classes and metadata for Salesforce production code.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG --skill platform-apex-test-generate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: platform-apex-test-generate
Source: https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG/tree/main/.agents/skills/platform-apex-test-generate
Command: npx skills add https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG --skill platform-apex-test-generate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the friction of designing, writing, and validating Salesforce Apex test classes by giving you a consistent pattern for production-ready coverage, reliable assertions, and repeatable fix loops.

Core Features & Use Cases

  • Test Class Generation: Creates focused Apex test classes with one behavior per method and matching metadata files.
  • Coverage and Bulk Validation: Supports trigger, service, controller, batch, queueable, selector, scheduled, callout, and platform event scenarios, including 251+ record bulk testing.
  • Mocking and Isolation: Guides TestDataFactory usage, callout mocking, SOSL mocking, and dependency injection patterns to keep tests deterministic.
  • Debugging and Fix Loops: Helps analyze failing tests, isolate root causes, and rerun focused tests until coverage and behavior are stable.

Quick Start

Ask for a Salesforce Apex test class for the target production class, and include the required TestDataFactory, metadata file, and coverage-focused validation pattern.

Frequently Asked Questions about platform-apex-test-generate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write Salesforce Apex test classes for triggers and batch jobs?

Generating Apex test classes for triggers and batch jobs requires one behavior per method, Assert-only validations, and 251+ record bulk testing. This pattern produces matching metadata files and reliable coverage for asynchronous workflows.

What is the best way to mock Apex callouts and SOSL in Salesforce tests?

Mocking Apex callouts and SOSL in Salesforce tests requires dependency injection and callout mocking patterns to keep tests deterministic. Using a TestDataFactory ensures consistent isolation across service and controller workflows.

How do I structure a TestDataFactory for Salesforce Apex test coverage?

Structuring a TestDataFactory for Salesforce Apex test coverage involves generating reusable mock data for bulk 251+ record validation. This ensures deterministic testing across trigger, selector, and platform event workflows.

Can I test queueable Apex and platform events with 251+ bulk records?

Yes, you can test queueable Apex and platform events with 251+ bulk records. This testing pattern enforces bulk validation and Assert-only checks to ensure asynchronous processes handle large data volumes reliably.

Why does my Salesforce Apex test class fail to cover scheduled and selector workflows?

Salesforce Apex test classes fail to cover scheduled and selector workflows when lacking deterministic mocking and isolated TestDataFactory usage. Applying targeted fix loops isolates root causes and reruns focused tests until coverage stabilizes.