Often, it seems that the answer to why do we write unit tests is because Salesforce makes us do it! This, however, is not the reason we should be writing unit tests. All classes in production orgs have to have 75% code coverage and all triggers must have some coverage. Salesforce enforces this for a number of reasons. As the platform evolves and new features are added, Salesforce needs to ensure that your applications will continue to run without an issue. To do this, they employ the hammer, a specialized test harness that allows them to run every unit test in every org twice. First, the hammer runs every test in every org on the current version of the platform. These same tests are then run on the pre-release version of the platform. This helps them ensure that your code not only runs on the new version of the platform, but that it also runs at least as efficiently as it did on the earlier platforms. Even if your unit tests have no assertions and utterly fail...
Mastering Application Development with Force.com
By :
Mastering Application Development with Force.com
By:
Overview of this book
Force.com 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 salesforce.com's Force.com 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 Force.com. It gets you started with a quick refresher of Force.com'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 Force.com 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 Force.com platform.
Table of Contents (16 chapters)
Mastering Application Development with Force.com
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Free Chapter
A Conceptual Overview of Application Development on the Salesforce1 Platform
Architecting Sustainable Triggers Using a Trigger Framework
Asynchronous Apex for Fun and Profit
Lightning Concepts
Writing Efficient and Useful Unit Tests
Deploying Your Code
Using, Extending, and Creating API Integrations
Team Development with the Salesforce1 Platform
My Way – A Prescriptive Discussion of Application Development on Salesforce1
Index
Customer Reviews