Book Image

Mastering Apex Programming

By : Paul Battisson
5 (1)
Book Image

Mastering Apex Programming

5 (1)
By: Paul Battisson

Overview of this book

As applications built on the Salesforce platform are now a key part of many organizations, developers are shifting focus to Apex, Salesforce’s proprietary programming language. As a Salesforce developer, it is important to understand the range of tools at your disposal, how and when to use them, and best practices for working with Apex. Mastering Apex Programming will help you explore the advanced features of Apex programming and guide you in delivering robust solutions that scale. This book starts by taking you through common Apex mistakes, debugging, exception handling, and testing. You'll then discover different asynchronous Apex programming options and develop custom Apex REST web services. The book shows you how to define and utilize Batch Apex, Queueable Apex, and Scheduled Apex using common scenarios before teaching you how to define, publish, and consume platform events and RESTful endpoints with Apex. Finally, you'll learn how to profile and improve the performance of your Apex application, including architecture trade-offs. With code examples used to facilitate discussion throughout, by the end of the book, you'll have developed the skills needed to build robust and scalable applications in Apex.
Table of Contents (21 chapters)
1
Section 1 – Triggers, Testing, and Security
8
Section 2 – Asynchronous Apex and Apex REST
15
Section 3 – Apex Performance

Summary

In this chapter, we have dealt with the importance of testing our Apex code and how we can improve the quality and integrity of our tests. Testing is a key part of the software development life cycle, and writing clear and well-structured tests that validate assumptions and outcomes through assertions is extremely important in providing confidence in your system.

We also saw how we can improve the creation of test data for our tests in a number of ways. The largest performance problem for Apex tests is the repeated creation of data in different unit tests, as the system must run through the save order of execution multiple times, taking up time and governor resources. By separating our test data into a factory, we can ensure that data is created in a consistent manner and save ourselves additional rework should the code need updating to accommodate new required fields and processing. Calling our test data creation from a method annotated by @TestSetup ensures that the data...