Book Image

Mastering Application Development with

By : Kevin J. Poorman
Book Image

Mastering Application Development with

By: Kevin J. Poorman

Overview of this book is an extremely powerful, scalable, and secure cloud platform, delivering a complete technology stack, ranging from databases and security to workflow and the user interface. With's cloud platform, you can build any business application and run it on your servers. The book will help you enhance your skillset and develop complex applications using It gets you started with a quick refresher of's development tools and methodologies, and moves to an in-depth discussion of triggers, bulkification, DML order of operations, and trigger frameworks. Next, you will learn to use batchable and schedulable interfaces to process massive amounts of information asynchronously. You will also be introduced to Salesforce Lightning and cover components—including backend (apex) controllers, frontend (JavaScript) controllers, events, and attributes—in detail. Moving on, the book will focus on testing various apex components: what to test, when to write the tests, and—most importantly—how to test. Next, you will develop a changeset and use it to migrate your code from one org to another, and learn what other tools are out there for deploying metadata. You will also use command-line tools to authenticate and access the Rest sObject API and the Bulk sObject API; additionally, you will write a custom Rest endpoint, and learn how to structure a project so that multiple developers can work independently of each other without causing metadata conflicts. Finally, you will take an in-depth look at the overarching best practices for architecture (structure) and engineering (code) applications on the platform.
Table of Contents (16 chapters)
Mastering Application Development with
About the Author
About the Reviewers

What not to test?

I'm often asked by developers who are new to the platform what kinds of thing they should write unit tests for. In general, I find that question rather frustrating. Many factors go into answering that question, and without knowing the specifics of your org, it's impossible to answer comprehensively. On the other hand, it's much easier to answer the question what not to test? While the answer to that question isn't cut and dry either, it's at least simpler to provide guidelines for. With that in mind, here are some things you should most likely not test.

Managed package code

Managed packages have to provide their own unit tests. Additionally, you don't get to see the code from managed packages, so writing unit tests for managed package code is not only difficult, it's fruitlessly redundant as well. However, this isn't carte blanche for not testing your code that interacts with the managed package code. The only time I write unit tests for managed package code, is when I'm...