Apex Code Testing and Coverage Best Practices - Amazon S3

27 Pages·2011·2.56 MB·English

by  Kavindra Patel

Apex Code Testing and
Coverage Best Practices

Ryan Spraetz
Product Manager
Anand B Narasimhan
Principal Consultant
Got Twitter?
@forcedotcom / #forcewebinar
Facebook?

facebook.com/forcedotcom

‘Like’ us in the month of March and enter to win an iPod Touch
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 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, 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 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, 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 filed on February 24, 2011 and in other filings with the
Securities and Exchange Commission. These documents 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 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.
P
Join the conversation on Twitter: #forcewebinar @forcedotcom
Agenda
  Testing philosophy
  Introduction to Apex Testing
  Writing tests and test tools
  Testing best practices and patterns
  Testing anti-patterns
  Testing Roadmap
Join the conversation on Twitter: #forcewebinar @forcedotcom
Testing Philosophy
  Testing is key to successful development
  Testing requirements
–  75% code coverage
–  Strive for better
  Automation, automation, automation
–  Test suites catch regressions
–  Manual testing does not scale!
  Apex Test Hammer
–  Your 8M tests are part of our release process
Join the conversation on Twitter: #forcewebinar @forcedotcom
How do I test my code?
  Testmethods! How easy is that?
public class HelloDevs{ @isTest
private class TestHelloDevs{
public static String getGreeting(){
return (‘Test Away!’); static testmethod void testGreeting(){
} String gr = HelloDevs.getGreeting();
System.assertEquals(‘Test Away!’,gr);
static testmethod void testGreeting(){ }
String gr = HelloDevs.getGreeting(); }
System.assertEquals(‘Test Away!’,gr);
}
}
  Can only be called from test code
  @isTest classes do not count towards code size limits
Join the conversation on Twitter: #forcewebinar @forcedotcom
Anatomy of a TestMethod
Demo
public class AccountProcessor{
public static Account ProcessAccount(Account acc){
//Do work here, for example:
acc.numberOfEmployees = 10;
return acc;
}
public static testmethod void testProcessAccount(){
//Create test data
Account acc = new Account(name = ‘testAccount’);
//Run the code you want to test
Test.startTest();
acc = ProcessAccount(acc);
Test.stopTest();
//Assert results
System.assertEquals(acc.numberOfEmployees, 10);
}
}
Additional Resources on Apex Test classes and Test Methods

  How to Write Good Unit Tests

  Apex Developer Guide
Join the conversation on Twitter: #forcewebinar @forcedotcom
Verifying my code
  System.assert();
  System.assertEquals();
If you are not using asserts in your test code, you are
probably not writing effective tests!
Join the conversation on Twitter: #forcewebinar @forcedotcom
Special System functions for testing
  System.runAs(User){ }
  Test how your code interacts with your organization’s
sharing model
  Does not mimic CRUD/FLS
public class TestAsUser{
public static testmethod void testAsUser(){
User u = [SELECT id FROM User LIMIT 1];
System.runAs(u){
//Code here will respect sharing model
}
}
}
Join the conversation on Twitter: #forcewebinar @forcedotcom
Special System functions for testing
  Test.StartTest() and Test.StopTest()
  Extra set of governor limits to test your processes
public class TestAsUser{
public static testmethod void testProcess(){
//Do data set up here
insert new Account(name = ‘test’);
//Do your testing here
Test.startTest();
ProcessAccounts();
Test.stopTest();
//Do your aserts here
System.assert(…)
}
}
Join the conversation on Twitter: #forcewebinar @forcedotcom