Yamamuro Atsushi presented the Apex 10 Commandments which provide best practices for writing efficient and testable Apex code. The commandments include: only putting one trigger per object; utilizing maps for queries; aiming for 100% test coverage with assertions; limiting future calls and using asynchronous code where possible; and researching session content before attending conferences.

1. TerraSky Power Night 2013/12/05
Apex 10 Commandments

2. 最初に自己紹介
やまむろ あつし
1

3. Apex 10 Commandments
2

4. #1 Thou shalt not put queries in for loops
3

5. #2 Thou shalt not put DML in for loops
4

6. #3 Thou shalt have a happy balance
between clicks & code
5

7. #4 Thou shalt only put one trigger per object
#5 Thou shalt not put code in triggers other than
calling methods and managing execution order
6

8. #6 Thou shalt utilize maps for queries
wherever possible
7

9. #7 Thou shalt make use of relationships to
reduce queries wherever possible
8

10. #8 Thou shalt aim for 100% test coverage
In general test your methods for:
 Positive effects.
• Given proper input it should act like this.
• Not just happy path, but all logic branches.
 Negative effects.
• Given bad data it should error like this.
 Role/Profile/User effects
• Given a user with X profile and Y role it should
act like this.
9

11. #9 Thou shalt write meaningful and useful tests
It’s not a test without assertions.
 Assert(A==B, “Reason for Assert failure”)
 AssertEquals(A,B, “Reason for Assert failure”)
 AssertNotEquals(A,B, “Reason for Assert
failure”)
10

12. #10 Thou shalt limit future calls and use
asynchronous code where possible
In general bias towards batch apex
 Ensure it runs as efficiently as possible.
 If you need @future methods.
11

13. #11 Research the session content beforehand
If you go to Dreamforce・・・
12