---
schema_version: "1"
id: 54d360205a4936285487cd9ebcbe3b3625c0ba4a77eb9c368f3a7974917b1adf
title: Apex Hammer Test Results
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/apex_hammer_execution_status.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.apex_hammer_execution_status.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a91f61824ad9d44b99c99e034f9aa8db5fd8bf3db81615059788b11a9343305b
description: With the Hammer process, Salesforce runs your org’s Apex tests in both the current and new release, and compares the results to identify issues for you.
products:
  - Salesforce Platform
release: "264"
---
# Apex Hammer Test Results

With the Hammer process, Salesforce runs your org’s Apex tests in both the current and new release, and compares the results to identify issues for you.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Salesforce Classic (<a href="https://help.salesforce.com/s/articleView?id=xcloud.overview_edition_lex_only.htm&amp;type=5&amp;language=en_US" target="_blank">not available in all orgs</a>)</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</td></tr></tbody></table>

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_code-264-0-0-production-enus/789bc523-706b-4ae4-8fe9-be6322e38b6b/images/icon_important.png)

Important

- Maintaining the security of your data is our highest priority. We don’t view or modify any data in your org, and all testing is done in a copy that runs in a secure data center.
- We triage bugs based on certain criteria and make every effort to fix them all before release.
- The Hammer process isn’t guaranteed to run in all or most orgs. It sometimes doesn’t run in any orgs, or runs in only a small subset of orgs.
- Apex Hammer test results aren’t available in Government Cloud orgs.

## Access Apex Hammer Test Results

To access Apex Hammer test results, from Setup, in the Quick Find box, enter **Apex Hammer Test Results** and select it. If the Apex Hammer Test Results page isn’t viewable in Setup, then Apex Hammer isn’t available for this org.

The page shows the results of running Apex tests for this org as part of the Apex Hammer process. This process runs your org’s Apex tests in both the current and new release, and compares the results. Salesforce uses these results to identify any issues to resolve before the release.

This data is shown on the page.

- Date when Hammer last ran in this org
- Number of Apex tests executed and passed
- Percentage of Apex tests that are data silo tests
- Date range when Hammer is scheduled to run next

## Create Data Silo Tests

A data silo test is a test method that doesn’t have access to org data. The advantages of creating data silo tests are:

- Tests run more reliably because they aren’t dependent on data that can sometimes change.
- Failures from those tests are easier to diagnose.
- Finding bugs in the Hammer process is easier.
- Deploying from one org to another is more reliable.

You can make a test run in this preferred manner by using the default behavior. Test methods only use org data when they’re annotated with `isTest(SeeAllData=true)` or in a test class annotated with `isTest(SeeAllData=true)`. Data silo tests are supported in API version 24.0 and later. See [Isolation of Test Data from Organization Data in Unit Tests](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_testing_data_access.htm).

We highly recommend that as many of your tests as possible be data silo tests. The higher the percentage of data silo tests, the more effective the Hammer process is in finding potential issues in our code base. These issues can affect your org. This early detection enables Salesforce to identify and resolve bugs before we release new software.

We encourage you to write all new Apex tests as data silo tests and convert existing tests to data silo tests.