Adherents of test-driven development argue for writing the tests first. Indeed, the idea behind test-driven development is that tests define acceptance of code. In general, the Test-driven development (TDD) approach is to write a test, see it fail, and then write just enough code to make the test pass. In practice, this is easier said than done. Others argue that you should write your code and then the tests because it's more efficient. I find the most successful developers almost always develop the code and the tests simultaneously, the code influencing the tests and the tests ensuring that the code is written in a maintainable, testable way. So long as the tests are written, and written well, I find it hard to argue for or against writing the tests first. Indeed, I find it most flexible to write the tests at the same time as the code. The central question of unit testing your code isn't when to test or what to test, but how to test.
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.
Related Content you might be interested in
Current Title:
Mastering Application Development with Force.com
No titles found
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