Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Advanced Testing and Debugging using the Developer Console webinar

2,595 views

Published on

The Developer Console is your one-stop shop for developing on the Force.com platform. This application allows you to author and debug Apex code, create Visualforce pages, run tests on your programmatic artifacts, and to inspect your org data via query.

Join us as we dig deeper into the comprehensive debugging, profiling, and testing capabilities of the Developer Console.

Watch this webinar to:

Learn how to run tests using the Developer Console
See how to examine log results using the Developer Console
Understand how to analyze the performance of your org’s operations
Learn about checkpoints, the Force.com equivalent of breakpoints, for debugging
Explore the query editor functionality to get better access to your data

  • Be the first to comment

Advanced Testing and Debugging using the Developer Console webinar

  1. 1. Advanced Testing & DebuggingGetting the Most from the Developer ConsoleJosh Kaplan, Salesforce.com, Sr. Product Manager@Josh SFDCTony Tonev, Salesforce.com, Software Engineer
  2. 2. Safe harbor 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 intellectual property and other litigation, risks associated with 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-Q for the most recent fiscal quarter ended July 31, 2012. This 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.Join the conversation: #forcewebinar
  3. 3. Speakers Josh Kaplan Tony Tonev Sr. Product Manager, Software Engineer @JoshSFDCJoin the conversation: #forcewebinar
  4. 4. Follow Developer Force for the latest news @forcedotcom / #forcewebinar Developer Force – Force.com Community +Developer Force – Force.com Community Developer Force Developer Force groupJoin the conversation: #forcewebinar
  5. 5. Have questions? §  We have an expert support team at the ready to answer your questions during the webinar. §  Ask your questions via the GoToWebinar Questions Pane. §  The speaker(s) will choose top questions to answer live at the end of the webinar. §  Please post your questions as we go along! §  Only post your question once; we’ll get to it as we go down the list.Join the conversation: #forcewebinar
  6. 6. Agenda §  Testing Apex •  Why test? •  When test? •  How test? §  Code Coverage §  Advanced Debugging •  Log Inspector •  Checkpoints –  Set checkpoints –  View memory contents –  Inject logicJoin the conversation: #forcewebinar
  7. 7. Assumptions This webinar assumes the following: §  You know… •  …what Apex code is •  …how to launch the Developer Console §  You have… •  …used the Developer Console before •  …done debugging before But don’t worry, you can catch up via these resources: http://wiki.developerforce.com/page/Webinar:_Intro_to_Apex_Code_(2012-July)Join the conversation: #forcewebinar
  8. 8. Why test?Join the conversation: #forcewebinar
  9. 9. Testing Protects You From OthersJoin the conversation: #forcewebinar
  10. 10. Testing Protects You From UsJoin the conversation: #forcewebinar
  11. 11. When should I test? Write tests throughout development §  Before development §  After development §  In their own @isTest classes You should test frequently! §  During development §  Before deployment §  During deployment §  During release preview windowJoin the conversation: #forcewebinar
  12. 12. How can I run tests on my code? Salesforce provides several avenues for test execution §  Developer Console §  “Setup” User Interface §  Automatically during deployment §  Through the Tooling API *COMING SOON!*Join the conversation: #forcewebinar
  13. 13. Developer ConsoleJoin the conversation: #forcewebinar
  14. 14. Testing in “Setup” User InterfaceJoin the conversation: #forcewebinar
  15. 15. Asynchronous Test Execution Salesforce runs your tests in the background so they can be processed as resources allow. §  Asyncronous testing runs tests in no particular order §  It allows you to see status of tests as they complete §  The process is integrated into developer consoleJoin the conversation: #forcewebinar
  16. 16. Code Coverage We store the results of your testing to calculate code coverage, and show you these stored results in the developer console. §  Aggregate coverage for each class and trigger §  Coverage by each test method on each class and trigger §  CAUTION! These results are stale as soon as you change the test or the classJoin the conversation: #forcewebinar
  17. 17. Let’s See The Demo Already!Join the conversation: #forcewebinar
  18. 18. Use Case: UberJetJoin the conversation: #forcewebinar
  19. 19. Debugging CodeJoin the conversation: #forcewebinar
  20. 20. Debugging with the Log Inspector §  Execution Log •  The entire transaction, line by line and more §  Source / Variables •  Current code location and variable values §  Stack •  How you got where you are •  How long each step took §  Execution Overview •  Limits •  Performance per action, per methodJoin the conversation: #forcewebinar
  21. 21. When the log is not enough…checkpoints! A checkpoint is like a breakpoint, but cloud-approved §  Heap •  Provide a view into the memory at the checkpoint §  SOQL query •  Run a SOQL query at the checkpoint §  Apex Code •  Inject a miniature apex snippet at the checkpointJoin the conversation: #forcewebinar
  22. 22. Recap §  Testing Is Important, Testing Is Easy •  Test always •  Use the Developer Console to see results and code coverage statistics §  Debugging Is Hard, Debugging Can Be Easier •  The Log Inspector provides many views into the haystack •  Use Checkpoints to see the state of the world at a critical pointJoin the conversation: #forcewebinar
  23. 23. Resources §  Developer Console topic page: http://wiki.developerforce.com/page/Developer_Console §  Next Steps •  Write More Tests! •  Use Developer Console To Run Your Tests •  Use Developer Console To Debug Your CodeJoin the conversation: #forcewebinar

×