You're reading from Salesforce Platform Enterprise Architecture- fourth edition A must-read guide to help you architect and deliver packaged applications for enterprise needs

Product type Paperback

Published in Mar 2023

Publisher Packt

ISBN-13 9781804619773

Length 712 pages

Edition 4th Edition

Languages

Java

Tools

Salesforce

Concepts

Solution Architecture

Author (1):

Andrew Fawcett

View More author details

Table of Contents (23) Chapters

Preface

1. Part I: Key Concepts for Application Development

2. Building and Publishing Your Application FREE CHAPTER

3. Leveraging Platform Features

4. Application Storage

5. Apex Execution and Separation of Concerns

6. Part II: Backend Logic Patterns

7. Application Service Layer

8. Application Domain Layer

9. Application Selector Layer

10. Additional Languages, Compute, and Data Services

11. Part III: Developing the Frontend

12. Building User Interfaces

13. User Interfaces and the Lightning Component Framework

14. Part IV: Extending, Scaling, and Testing an Application

15. Providing Integration and Extensibility

16. Asynchronous Processing and Big Data Volumes

17. Unit Testing

18. Source Control and Continuous Integration

19. Integrating with External Services

20. Adding AI with Einstein

21. Other Books You May Enjoy

22. Index

Unit testing versus system testing

When it comes to testing Apex code, we know the drill: write good tests to cover your code, assert its behavior, and obtain at least 75% coverage. The Salesforce Platform will not allow you to deploy or package code for a production environment unless you obtain this amount of code coverage or higher. You also must cover your Apex Trigger code, even if it’s only a single line, as you will soon see is the case with the implementation of the Apex Triggers in this book.

It is not just for sake of good practice that Salesforce requires 75% coverage; Salesforce runs all Apex tests uploaded to the platform as part of its internal platform regression testing strategy. They look for the difference in test results (regardless of if your test passes or fails) between the current production version of the platform and the upcoming release. This way, Salesforce can find and fix regressions in the platform before even rolling out the platform...