squash bugs with the apex debugger (tdx'17)

18
Vivek M. Chawla Danny Chang Squash Bugs with the Apex Debugger

Upload: vivek-chawla

Post on 23-Jan-2018

116 views

Category:

Technology


7 download

TRANSCRIPT

Page 1: Squash Bugs with the Apex Debugger (TDX'17)

Vivek M. ChawlaDanny Chang

Squash Bugs with theApex Debugger

Page 2: Squash Bugs with the Apex Debugger (TDX'17)

#TDX17

@VivekMChawla @DannySFDC

Danny ChangAssociate ISV Technical

Evangelist

Vivek M. ChawlaSenior ISV Technical

Evangelist

Page 3: Squash Bugs with the Apex Debugger (TDX'17)

Agenda

• What is the Apex Debugger?

• Setup and Start a Debugging Session

• Demo – Apex Debugger in Action

• Special Considerations and the Debugger Roadmap

Page 4: Squash Bugs with the Apex Debugger (TDX'17)

Forward-Looking StatementsStatement 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. coulddiffer materially from the results expressed or implied by the forward looking statements we make. All statements other than statements of historical factcould be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financialitems 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 ourservice, 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 anypossible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, andmotivate 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 financialresults 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 themost recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the InvestorInformation section of our Website.

Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currentlyavailable and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisionsbased upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to updatethese forward-looking statements.

Page 5: Squash Bugs with the Apex Debugger (TDX'17)

What is the Apex Debugger?

Page 6: Squash Bugs with the Apex Debugger (TDX'17)

Advantages of an Interactive Debugger

SetBreakpoints

Single-Step Execution

View Variables & Call Stack

Page 7: Squash Bugs with the Apex Debugger (TDX'17)

Debug Logs vs. Interactive Debugging

VS

Page 8: Squash Bugs with the Apex Debugger (TDX'17)

0

Sandbox Orgs

The Two Flavors of Apex Debugger

Standard Apex Debugger ISV Customer Debugger

Sandbox Orgs

ISV (License Management Org) ISV Customer (Production Org)Production Org

ISVDeveloper

CustomerDeveloper

1DebugLicense 01ISV Debug

License

Page 9: Squash Bugs with the Apex Debugger (TDX'17)

Setup and Start a Debugging Session

Page 10: Squash Bugs with the Apex Debugger (TDX'17)

Set up the Apex Debugger

1. Make sure your org has access to the Apex Debugger

2. Install or update the Force.com IDE plug-in for Eclipse

3. Create a permission set for Apex Debugger users

Page 11: Squash Bugs with the Apex Debugger (TDX'17)

Start a Debugging Session

1. Create project and connect to your sandbox org

2. Create a new Debug Configuration and apply to your project

3. Launch the Debug Configuration

Page 12: Squash Bugs with the Apex Debugger (TDX'17)

Start an ISV Customer Debugging Session

Drag the Debug Icon from setup to Eclipse

“Login as” Customer from Subscriber Console

Navigate to the Apex Debugger setup page

Page 13: Squash Bugs with the Apex Debugger (TDX'17)

#TDX17

Demo – Apex Debugger in Action

Page 14: Squash Bugs with the Apex Debugger (TDX'17)

Special Considerations andthe Debugger Roadmap

Page 15: Squash Bugs with the Apex Debugger (TDX'17)

Special Considerations when Using the Debugger

• Debugging allowed on Sandbox pods only

• No support for asynchronous code

• Certain actions will kill your debugging session– Any action that recompiles metadata– Installing / uninstalling a package

• Beware of orphaned sessions

Page 16: Squash Bugs with the Apex Debugger (TDX'17)

Apex Debugger Roadmap

Debug Against Scratch Orgs

Allow Debugging From Other IDEs

Keep Expanding Access

Page 17: Squash Bugs with the Apex Debugger (TDX'17)
Page 18: Squash Bugs with the Apex Debugger (TDX'17)