Intro to Apex Testing - Dreamforce 2016
- 1. Introduction to Apex Testing [email protected] @meerkatz [email protected] Laura Meerkatz Developer Salesforce.org Adam Lincoln Developer Salesforce.org
- 2. Forward-Looking Statements 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.
- 3. Agenda Why do we write tests? What to test Best practices Resources Q&A 1 2 3 4 5
- 4. Poll!
- 5. Why do we test?
- 6. Test basics
- 7. What goes into each test class Test Structure
- 8. What to test
- 9. What to test Things that should happen do happen (positive) Things that shouldn’t happen don’t happen (negative) User access Exceptions Bulk testing 1 2 3 4 5
- 10. Calculate employee bonuses Sample scenario • Employees are awarded a 1% bonus based on the amount of closed won opportunities they own • The maximum bonus is $25,000 • Only admins can retotal bonuses • A negative total opportunity amount should result in an exception
- 11. Verify that the things that should happen do happen Positive Tests
- 12. Verify that the things that should happen do happen Positive Tests
- 13. Verify that the things that should not happen don’t happen Negative Tests
- 14. Verify that the things that should not happen don’t happen Negative Tests
- 15. Verify that users can’t do things they don’t have permission to do Use System.runAs() to test user access
- 16. Verify when your code should be throwing an exception Exception Testing
- 17. Verify that your code will work when several records are updated at once Bulk Testing
- 18. Test Data
- 19. Avoid using SeeAllData=true Create data for tests
- 20. Sometimes you have to use SeeAllData=true There are exceptions
- 21. Set up your test data in one place so you can reuse it everywhere Use Test Data Factories
- 22. Set up test data for all methods in one place Use @TestSetup
- 23. Reset governor limits Use Test.startTest()/Test.stopTest()
- 24. Running Tests
- 25. Summary • Tests help you sleep better at night! • Test for things that should happen and things that shouldn’t happen • Use test data factories and @TestSetup to make creating test data easy • Use developer console to run individual tests and see coverage
- 27. Questions?
- 28. Thank Y u
Editor's Notes
- #3: Key Takeaway: We are a publicly traded company. Please make your buying decisions only on the products commercially available from Salesforce. Talk Track: Before I begin, just a quick note that when considering future developments, whether by us or with any other solution provider, you should always base your purchasing decisions on what is currently available.
- #5: Who here is an Apex dev? Who here has written Apex tests? Who feels like they’re writing good tests?
- #9: Positive Negative Access Exception Bulk
- #11: For our sample code, we’re testing to see that employees are awarded a certain amount based on the amount of closed won opportunities they own.
- #20: Off by default Makes assertions easier Avoid row lock exceptions Makes tests run faster
- #21: By default SeeAllData is false. When SeeAllData is set to true, test methods have access to all data in the organization. This can lead to row lock errors that prevent users from updating records because those records are currently being accessed in tests.
- #22: Also: Use Test.loadData() to load data from csvs stored as static resources
- #23: Runs once before all test methods Changes roll back between tests
- #24: Also forces async calls to run sychronously
- #25: demo