Apex Developer Guide

Apex Developer Guide
Release Notes
Getting Started with Apex
Writing Apex
Data Types and Variables
Control Flow Statements
Classes, Objects, and Interfaces
Classes
Interfaces
Keywords
Annotations
AuraEnabled Annotation
Deprecated Annotation
Future Annotation
IntegrationTest Annotation (Developer Preview)
InvocableMethod Annotation
InvocableVariable Annotation
IsTest Annotation
JsonAccess Annotation
NamespaceAccessible Annotation
ReadOnly Annotation
RemoteAction Annotation
SuppressWarnings Annotation
TestSetup Annotation
TearDown Annotation (Developer Preview)
TestVisible Annotation
Apex REST Annotations
Classes and Casting
Differences Between Apex Classes and Java Classes
Class Definition Creation
Namespace Prefix
Apex Code Versions
Lists of Custom Types and Sorting
Using Custom Types in Map Keys and Sets
Working with Data in Apex
Document Your Apex Code
Running Apex
Debugging, Testing, and Deploying Apex
Apex Reference
Appendices
PDF

IntegrationTest Annotation (Developer Preview)

Use the IntegrationTest annotation to mark both classes and methods that are used in integration testing.

The Apex Integration Tests feature is available as a developer preview in scratch orgs in Summer ’26 (API version 67.0). The feature isn’t generally available unless or until Salesforce announces its general availability in documentation or in press releases or public statements. All commands, parameters, and other features are subject to change or deprecation at any time, with or without notice. Don't implement functionality developed with these commands or tools in your production package.

Note

A class annotated with @IntegrationTest can only contain integration test methods and @TearDown methods. You can't mix @IntegrationTest and @IsTest annotations on the same class.

Integration test methods cannot be called from non-test contexts or from @IsTest test methods. However, integration tests can call methods in @IsTest utility classes, for example, shared test data factories.