Running Unit Test Methods

1. From Setup, click Develop | Apex Test Execution.
2. Click Select Tests....

   If you have Apex classes that are installed from a managed package, you must compile these classes first by clicking Compile all classes on the Apex Classes page so that they appear in the list. See Managing Apex Classes.

   Note

3. Select the tests to run. The list of tests includes only classes that contain test methods.
   • To select tests from an installed managed package, select its corresponding namespace from the drop-down list. Only the classes of the managed package with the selected namespace appear in the list.
   • To select tests that exist locally in your organization, select [My Namespace] from the drop-down list. Only local classes that aren't from managed packages appear in the list.
   • To select any test, select [All Namespaces] from the drop-down list. All the classes in the organization appear, whether or not they are from a managed package.

   Classes with tests currently running don't appear in the list.

   Note

4. Click Run.

1RunTestsResult[] runTests(RunTestsRequest ri)

For more information on runTests(), see the WSDL located at https://your_salesforce_server/services/wsdl/apex, where your_salesforce_server is equivalent to the server on which your organization is located, such as na1.salesforce.com.

Though administrators in a Salesforce production organization cannot make changes to Apex code using the Salesforce user interface, it is still important to use runTests() to verify that the existing unit tests run to completion after a change is made, such as adding a unique constraint to an existing field. Salesforce production organizations must use the compileAndTest SOAP API call to make changes to Apex code. For more information, see Deploying Apex.

For more information on runTests(), see SOAP API and SOAP Headers for Apex.

You can run tests asynchronously using ApexTestQueueItem and ApexTestResult. Using these objects and Apex code to insert and query the objects, you can add tests to the Apex job queue for execution and check the results of completed test runs. This enables you to not only start tests asynchronously but also schedule your tests to execute at specific times by using the Apex scheduler. See Apex Scheduler for more information.

To start an asynchronous execution of unit tests and check their results, use these objects:

• ApexTestQueueItem: Represents a single Apex class in the Apex job queue.
• ApexTestResult: Represents the result of an Apex test method execution.

Insert an ApexTestQueueItem object to place its corresponding Apex class in the Apex job queue for execution. The Apex job executes the test methods in the class. After the job executes, ApexTestResult contains the result for each single test method executed as part of the test.

To abort a class that is in the Apex job queue, perform an update operation on the ApexTestQueueItem object and set its Status field to Aborted.

If you insert multiple Apex test queue items in a single bulk operation, the queue items will share the same parent job. This means that a test run can consist of the execution of the tests of several classes if all the test queue items are inserted in the same bulk operation.

The maximum number of test queue items, and hence classes, that you can insert in the Apex job queue is the greater of 500 or 10 multiplied by the number of test classes in the organization. For sandbox and Developer Edition organizations, this limit is higher and is the greater of 500 or 20 multiplied by the number of test classes in the organization.

1swfobject.registerObject("clippy.codeblock-1", "9");public class TestUtil {
2
3    // Enqueue all classes ending in "Test". 
4    public static ID enqueueTests() {
5        ApexClass[] testClasses = 
6           [SELECT Id FROM ApexClass 
7            WHERE Name LIKE '%Test'];
8        if (testClasses.size() > 0) {
9            ApexTestQueueItem[] queueItems = new List<ApexTestQueueItem>();
10            for (ApexClass cls : testClasses) {
11                queueItems.add(new ApexTestQueueItem(ApexClassId=cls.Id));
12            }
13
14            insert queueItems;
15
16            // Get the job ID of the first queue item returned.
17            ApexTestQueueItem item = 
18               [SELECT ParentJobId FROM ApexTestQueueItem 
19                WHERE Id=:queueItems[0].Id LIMIT 1];
20            return item.parentjobid;
21        }
22        return null;
23    }
24
25    // Get the status and pass rate for each class
26    // whose tests were run by the job.
27    // that correspond to the specified job ID.
28    public static void checkClassStatus(ID jobId) {
29        ApexTestQueueItem[] items = 
30           [SELECT ApexClass.Name, Status, ExtendedStatus 
31            FROM ApexTestQueueItem 
32            WHERE ParentJobId=:jobId];
33        for (ApexTestQueueItem item : items) {
34            String extStatus = item.extendedstatus == null ? '' : item.extendedStatus;
35            System.debug(item.ApexClass.Name + ': ' + item.Status + extStatus);
36        }
37    }
38
39    // Get the result for each test method that was executed.
40    public static void checkMethodStatus(ID jobId) {
41        ApexTestResult[] results = 
42           [SELECT Outcome, ApexClass.Name, MethodName, Message, StackTrace 
43            FROM ApexTestResult 
44            WHERE AsyncApexJobId=:jobId];
45        for (ApexTestResult atr : results) {
46            System.debug(atr.ApexClass.Name + '.' + atr.MethodName + ': ' + atr.Outcome);
47            if (atr.message != null) {
48                System.debug(atr.Message + '\n at ' + atr.StackTrace);
49            }
50        }
51    }
52}
53