tools-only Credits & Acknowledgments
This skill was built upon the collective wisdom of the Salesforce developer community. We gratefully acknowledge the following authors and resources whose ideas, patterns, and best practices have shaped this skill.
Authors & Contributors
James Simone
Key contributions:
- DML mocking pattern for fast tests
- Factory pattern for dependency injection
- Performant Apex test strategies
- Stub ID generation for test isolation
Referenced articles:
- Mocking DML
- Writing Performant Apex Tests
- Dependency Injection & Factory Pattern
- Mocking Apex History Records
- Testing Custom Permissions
Beyond the Cloud (Piotr Gajek)
Key contributions:
- Mocking vs Stubbing distinction
- Test Data Factory pattern with fluent interface
- Selector layer mocking strategies
- Query result mocking
Referenced articles:
Apex Hours (Amit Chaudhary)
Key contributions:
- Mocking framework fundamentals
- HttpCalloutMock patterns
- Test class best practices
Referenced articles:
Official Salesforce Resources
- Testing Best Practices: developer.salesforce.com/docs
- StubProvider Interface: Apex Reference Guide
- HttpCalloutMock Guide: Testing HTTP Callouts
- Trailhead: Apex Unit Testing
- Trailhead: Mock and Stub Objects
Key Patterns Integrated
| Pattern | Source | Integration |
|---|---|---|
| DML Mocking | James Simone | templates/dml-mock.cls |
| Mocking vs Stubbing | Beyond the Cloud | docs/mocking-patterns.md |
| Test Data Factory | Beyond the Cloud | docs/test-data-factory-guide.md |
| HttpCalloutMock | Apex Hours | templates/http-mock-response.cls |
| StubProvider | Salesforce Docs | templates/stub-provider-example.cls |
| Performant Tests | James Simone | docs/performance-optimization.md |
Philosophy
This skill integrates concepts and patterns from community resources, teaching Apex developers how to write fast, reliable, maintainable tests. The goal is to move beyond "75% coverage" toward true unit testing with proper isolation and mocking.
If we've missed anyone whose work influenced this skill, please let us know so we can add proper attribution.