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

Understanding the importance of testing

Through the years that I have been working in Salesforce, I have too often encountered the following scenarios:

  • Developer receives problem
  • Developer writes code
  • Developer tests through the user interface (UI)
  • They then declare the work as finished and hand over to testing team or customer for review
  • Developer writes test methods to achieve 75% code coverage
  • And then, developer deploys the code

The fact that the developer has declared the work as finished before the testing is complete is incorrect and should be discouraged as a practice. As a general rule, code without tests is not finished. A more correct order here would be the following:

  • Developer receives problem
  • Developer writes code
  • Developer writes test methods to achieve at least 95% code coverage
  • Developer tests through the UI
  • They then declare the work as finished and hand over to testing team or customer for review
  • Developer...