Join us to learn the components required for building a good unit test that will keep your developers and applications from being blindsided, as well as some of the common Apex use cases like controllers and triggers. You'll also see how to handle trickier situations like HTTP callouts and asynchronous processing.

1. Apex Testing Best Practices
Daniel Hoechst
Salesforce Developer, ARUP Laboratories
daniel@verticalcoder.com
@dhoechst

2. Safe harbor statement under the Private Securities Litigation Reform Act of 1995:
This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize
or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the
forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any
projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding
strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or
technology developments and customer contracts or use of our services.
The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality
for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and
rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with
completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our
ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment,
our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on
potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent
fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important
disclosures are available on the SEC Filings section of the Investor Information section of our Web site.
Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and
may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are
currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.
Safe Harbor

3. Daniel Hoechst
Salesforce Developer, ARUP Laboratories

4. • Why should you test
• How you should test
• Tips & Tricks – Demos!
What you’ll get out of this talk

5. • Find Mistakes
• Improve Code
• Regression Testing
• 75% Code Coverage
Why Test?

6. • Before each Salesforce release
• Manually by developer during development
• During a deploy to sandbox (if option selected)
• During a deploy to production(always)
When are Tests Run?

7. • Setup test data and other conditions
• Call method, insert data (test small pieces at a
time)
• Verify expected results
• (No need to cleanup test data.)
Testing Process

8. • Put all tests into their own classes
• Use @isTest annotation to identify test classes and test methods.
• Use asserts everywhere!
Testing Basics

9. • Always create your own test data, never rely on data already
existing in the org.
• Use a centralized test factory
https://github.com/dhoechst/Salesforce-Test-Factory
https://github.com/mbotos/SmartFactory-for-Force.com
• Tip: use @testSetup annotation to share setup across methods in
the same class
Setting Up Test Data

10. Use Asserts!
Create test data using a test factory
Use Test.startTest to reset limits
Our First Demo

11. Use @testVisible to test private methods
To test Exceptions, catch the exception and return. Never swallow an
exception without examining it and taking action.
Our First Demo

12. • Set up test data using test factory
• Use Test.startTest() to reset limits
• Test all permutations of data
• Contacts with and without emails
• Accounts with and without emails
• Test bulk insert of records (Data Loader and other tools can insert
up to 200 at a time)
Testing Triggers

13. • Use Test.startTest() to avoid “Uncommitted Work” exception
• Use MockHttpResponse to simulate the response
Testing Callouts

14. • You can’t interact with page directly
• Instantiate controller extensions with standard controller
• Check for error messages on page
• Assert that PageReferences return correct page
Testing Controllers

15. • Use to test “with sharing”
• Use to avoid mixed DML errors when setting up test conditions
Using Test.runAs()

16. • All source code used in demo on Github (http://bit.ly/
apextesting)
• Test everything!
• Did I mention Asserts?
Summary

17. Share Your Feedback, and Win a GoPro!
3
Earn a GoPro prize entry for
each completed survey
Tap the bell to take a
survey2Enroll in a session1

18. Thank you