# Default Apex Class Configuration

{% hint style="info" %}
**Important Note:** This article is for **Org Administrators** in particular. The actions discussed in this article are not available to general users.  
{% endhint %}

### Configure Default Apex Test Class for your Salesforce Org <a href="#configure-default-apex-text-class-for-your-salesforce-org" id="configure-default-apex-text-class-for-your-salesforce-org"></a>

To configure the default **Apex Test Class** for your Salesforce org, follow the below steps:&#x20;

1. Log in to your ARM account.
2. Hover your mouse over the Settings tab and click on the option: **`Salesforce Org`**.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fv16poBCbSL3WucrN4Nqe%2Fimage.png?alt=media&#x26;token=53a35f34-ba2a-401a-b3dd-a2abdc9d221a" alt="" width="267"><figcaption></figcaption></figure>

1. Select your **`Salesforce Org`** from the list and go to the **`Salesforce Org - Configure Default Apex Test Class`** section. While deploying through ARM, this works in sync with the **Run Test** based on the **Changes Test** level option. If ARM cannot find dependent test classes, these default classes will run as Specified Tests.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F23PcKLsSimh2JeQWuHcW%2Fimage.png?alt=media&#x26;token=e46c5b94-d65e-4467-9fef-b16c5f318ba2" alt=""><figcaption></figcaption></figure>

&#x20;    **`a. Fetch Current Set:`** This option fetches Apex and Test classes dependency. From the list     fetched, select the required Apex Test Class that you would like to configure and run into the Destination Org

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fjdc4ZDtkE6xlXlivYcAI%2Fimage.png?alt=media&#x26;token=52190403-2e15-40f3-8e9c-cf15320bdb25" alt=""><figcaption></figcaption></figure>

&#x20;    **`b. Auto-populate:`** This option will run all local tests and get the complete dependency map

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FYmKMAVS3cNjpV35H2e3n%2Fimage.png?alt=media&#x26;token=0db6dc44-9175-4853-b104-607df0a473ad" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FzmAZQZs92iHLWiGKH7cT%2FScreenshot%202026-02-18%20at%2012.25.47.png?alt=media&#x26;token=d80f9fb9-ddaf-4d27-a3ae-1323a32d7e7d" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
**Troubleshooting:** If it takes longer to fetch the test classes using Auto-Populate, refresh the status by clicking the![](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FrDrZuDGOIBnrhz2Lezi6%2Fimage.png?alt=media\&token=0b2b1daa-d124-474a-9bf1-029401aa85df)icon.
{% endhint %}

{% hint style="info" %}
**Important Note:** If Apex Tests are not being populated, follow the steps below to ensure that the **Store Only Aggregated Code Coverage** check box is unchecked:

1. Log in to your Salesforce org through the browser.
2. Go to **Setup**.
3. Use the **Quick Find/Search** box to open the **Apex Test Execution** page.<br>

![](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FA0txrxwDHUScpHXrenuP%2Fimage.png?alt=media\&token=7aec9a03-b482-480c-a7dc-3f6cadad3853)

4. Click on **Options**. The **Apex Test Execution Options** pop-up appears.

![](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FvcAFVfU5Xy9QOSMVWOER%2Fimage.png?alt=media\&token=5b3ad2b4-8804-42f5-aba4-2cb65be53c28)

5. Ensure that the **Store Only Aggregated Code Coverage** check box is unselected.
6. Click **OK**, and return to ARM.
   {% endhint %}

&#x20;    **`c. Add Manually:`**&#x4D;anually configure your default Apex Test class.

5. On the next auto-populated screen, enter the **`Apex Test Class`** name and **`Apex Class/Trigger`** name in the respective fields. Mark the Apex class as default, and select the **`Default`** checkbox for such a test class.
6. Click the **`Add`** button at the top right corner to add another Apex Class name, or click the **`Clone`** icon to copy the details of the previous Apex Class.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FBiTAz6FAqzdMx5MVYyfg%2Fimage.png?alt=media&#x26;token=109c5a89-e77b-4c8c-b1c7-c3dc2a20753c" alt="" width="563"><figcaption></figcaption></figure>

7. Click **`OK`**. You can find the manually added Apex class on the previous screen, i.e., the [**`Salesforce Org Management`**](https://knowledgebase.autorabit.com/product-guides/arm/registration/salesforce-org/salesforce-org-management) page.

### Manage Apex Class <a href="#manage-apex-class" id="manage-apex-class"></a>

Once you have added an Apex test class or classes, you can perform various actions:

1. Click the **`edit`** icon next to the class name to modify its contents in a simple editor.
2. Click the **`delete`** icon to delete the class from your organization. You can select individual test classes or all the apex test classes in one go.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FKEwI69IKC2nPOjz12ZXu%2Fimage.png?alt=media&#x26;token=0e7c3cd3-1d2a-4964-aa66-c74cfdc5a500" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Important Note:** For each code coverage operation executed for your Salesforce org, AutoRABIT will either update or append the Apex Test Class mapping dynamically. Therefore, to view the added or modified Apex Test classes once the code coverage operation is performed, the user must ensure to refresh its Salesforce org from the [**`Salesforce Org Management`**](https://knowledgebase.autorabit.com/product-guides/arm/registration/salesforce-org/salesforce-org-management) section.
{% endhint %}

## Bulk Management of Apex Test Mappings (New UI)

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fo0NRaalbwQlAW51uQ683%2FScreenshot%202026-02-18%20at%2012.27.16.png?alt=media&#x26;token=df73ae98-ce4a-485b-a27b-fefb1f845164" alt=""><figcaption></figcaption></figure>

#### Overview

ARM now supports bulk management of Apex Test Class mappings in the **New UI** using a **CSV file**. You can download the current mappings, edit them offline, and upload them back to replace the existing configuration. This reduces unnecessary test execution and improves CI/CD efficiency.

***

### A. Download Current Test Mappings (CSV)

1. **Open ARM (New UI)** and go to **Test Mapping**.
2. Click **Download Test Cases**.
3. Save the downloaded CSV file to your machine.

**What happens next**

* The downloaded file contains **all active mappings**.
* A **success message** appears after download.
* Download is available only to users with access.

**CSV Columns (supported / required)**

* **Sno**
* **Apex Test Class**
* **Apex Class/Trigger**

> Only these three columns are processed during import.

***

### B. Update the CSV File

1. Open the downloaded CSV file in Excel / Google Sheets / a CSV editor.
2. Update mappings as needed (add, remove, or modify rows).
3. Ensure the file remains in **CSV format** with the same column headers.
4. Save the file.

**Important**

* Keep column names exactly as provided.
* Avoid extra columns (they will be ignored or may cause validation issues depending on implementation).

***

### C. Upload Updated Test Mappings (Replace Existing Set)

1. In **Test Mapping** (New UI), click **Upload Test Cases**.
2. Select your edited **CSV** file.
3. ARM validates the file:
   * Checks CSV format
   * Checks required columns exist
   * Validates structure and entries
4. If validation passes, a **confirmation prompt** appears.
5. Click **Confirm** to proceed.

**If validation fails**

* Upload is stopped
* Clear error messages are shown
* Existing mappings remain unchanged

***

### D. What “Replace” Means (After Successful Upload)

After confirmation and successful upload:

* The **entire existing mapping set is replaced**
* Old mappings are **removed** and **no longer visible**
* Only the newly uploaded mappings are used moving forward
* **Partial updates are not supported**

***

### E. Automatic Backup (Safety Net)

ARM automatically keeps **one backup** of the previous file.

**How it works**

* On every successful upload, the current active file is stored as a **backup**
* Only **one backup version** is retained
* Backup is available only **after at least one successful import**
* When you upload again, the backup is **overwritten** with the most recent previous file

***

### F. Download Backup (If Needed)

1. Go to **Test Mapping** (New UI).
2. If a backup exists, click **Download Backup**.
3. Save the backup CSV locally.

***

### Key Notes

* Available only in the **New UI**
* **CSV only** is supported
* Only these columns are supported:
  * **Sno**
  * **Apex Test Class**
  * **Apex Class/Trigger**
* Every upload **replaces the full mapping set**
* Only **one backup** file is maintained at a time