Apex Developer Guide

Apex Developer Guide
Release Notes
Getting Started with Apex
Writing Apex
Running Apex
Debugging, Testing, and Deploying Apex
Debugging Apex
Testing Apex
Understanding Testing in Apex
What to Test in Apex
What Are Apex Unit Tests?
Understanding Test Data
Run Unit Test Methods
Testing Best Practices
Testing Example
Testing and Code Coverage
Code Coverage Best Practices
Build a Mocking Framework with the Stub API
Deploying Apex
Distributing Apex Using Managed Packages
Apex Reference
Appendices
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Testing Example

The following example includes cases for the following types of tests:

The test is used with a simple mileage tracking application. The existing code for the application verifies that not more than 500 miles are entered in a single day. The primary object is a custom object named Mileage__c. The test creates one record with 300 miles and verifies there are only 300 miles recorded. Then a loop creates 200 records with one mile each. Finally, it verifies there are 500 miles recorded in total (the original 300 plus the new ones). Here’s the entire test class. The following sections step through specific portions of the code.

Positive Test Case

The following steps through the above code, in particular, the positive test case for single and multiple records.

  1. Add text to the debug log, indicating the next step of the code:
  2. Create a Mileage__c object and insert it into the database.
  3. Validate the code by returning the inserted records:
  4. Use the Assert.areEqual method to verify that the expected result is returned:
  5. Before moving to the next test, set the number of total miles back to 0:
  6. Validate the code by creating a bulk insert of 200 records.
    First, add text to the debug log, indicating the next step of the code:
  7. Then insert 200 Mileage__c records:
  8. Use Assert.areEqual to verify that the expected result is returned:

Negative Test Case

The following steps through the above code, in particular, the negative test case.

  1. Create a static test method called runNegativeTestCases:
  2. Add text to the debug log, indicating the next step of the code:
  3. Create a Mileage__c record with 501 miles.
  4. Place the insert statement within a try/catch block. This allows you to catch the validation exception and assert the generated error message. Use the Assert.fail method to clearly assert that you expect the validation exception.
  5. Now use the Assert.areEqual and Assert.isTrue methods to do the testing. Add the following code to the catch block you previously created:

Testing as a Second User

The following steps through the above code, in particular, running as a second user.

  1. Before moving to the next test, set the number of total miles back to 0:
  2. Set up the next user.
  3. Add text to the debug log, indicating the next step of the code:
  4. Then insert one Mileage__c record:
  5. Validate the code by returning the inserted records:
  6. Use the Assert.areEqual method to verify that the expected result is returned: