The fast Apex test runtime for Salesforce developers.
LATdx accelerates Apex tests through automatic DML & SOQL mocking, transformation caching, and a resident daemon, all via one CLI.
It supports two adaptation modes: rapid execution, which skips deployment and runs transformed Apex anonymously for the inner-loop edit/run/inspect cycle, and test acceleration, which transforms the codebase for the standard Salesforce test runner so CI and platform-native runs benefit too. Both modes share the same simulation engine.
Find your path
| I want to… | Go to |
|---|---|
| Get from zero to a green test run | Quickstart |
| Execute one-shot Apex at near-API speed (no deploy) | Quickstart, rapid execution |
| Wire LATdx into CI or consume JSON output | Output & Integration |
| Configure org targeting and authentication | Authentication & Org Targeting |
| Tweak runtime knobs and pick a mode | Configuration & Modes |
| Recover from a stuck run or stale state | Troubleshooting |
Explore the docs
On a warm cache, rapid-execution latdx test run skips the deploy phase entirely. The first run is the slow one; subsequent runs reuse cached transformations and the resident daemon.
Two adaptation modes
- Rapid execution (
latdx test run): in-memory transformation plus anonymous Apex. No deployment and no managed-package install required for file-mode runs. Best for the inner-loop edit/run/inspect cycle. - Test acceleration (
latdx boost→ deploy →sf apex test run): transforms the codebase for the standard Salesforce test runner. Best for CI and orgs that must execute through the platform-native runner.
The Adaptation Lifecycle page covers when to pick which, and how adapt, boost, restore, clean, and uninstall fit together.
Scope note
This track is CLI-first. Editor and extension UX details are documented separately; see Output & Integration for pointers.
What’s next?
A linear path for new users:
- Install the CLI binary
- Run the Quickstart to get a green test run
- Configure modes to fit your workflow
- Hit a snag? Troubleshooting