From Setup, enter Application in the Quick Find box, select Application Test Execution, then click View Test History to view all test results for your org, not just tests that you have run. Test results are retained for 30 days after they finish running, unless cleared.
Required Editions
| Available in: Salesforce Classic (not available in all orgs) and Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, Developer, and Database.com Editions |
To show a filtered list of items, select a predefined list from the View drop-down list, or click Create New View to define your own custom views.To edit or delete any view you created, select it from the View drop-down list and click Edit.
Click View to view more details about a specific test run.
The debug log is automatically set to specific log levels and categories, which can't be changed in the Application Test Execution page.
| Category | Level |
|---|---|
| Database | INFO |
| Apex Code | FINE |
| Apex Profiling | FINE |
| Workflow | FINEST |
| Validation | INFO |
- Unit tests must cover at least 75% of your Apex code, and all of those tests must
complete successfully.
- When deploying Apex to a production organization, each unit test in your organization namespace is executed by default.
- Calls to
System.debugare not counted as part of Apex code coverage. - Test methods and test classes are not counted as part of Apex code coverage.
- While only 75% of your Apex code must be covered by tests, don’t focus on the percentage of code that is covered. Instead, make sure that every use case of your application is covered, including positive and negative cases, as well as bulk and single records. This approach ensures that 75% or more of your code is covered by unit tests.
- Every trigger must have some test coverage.
- All classes and triggers must compile successfully.