Inspect, set, and reset LATdx configuration; switch between adaptation modes.

LATdx separates two distinct concerns: which adaptation mode you run tests through, and what configuration the CLI reads to decide how to execute. This page covers both: the latdx config surface, the supported configuration scopes, and the modes / strategies / profiles you can flip per run.

Adaptation modes

LATdx supports two adaptation modes that share the same transformation engine but differ in what gets deployed and how the tests execute:

• 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. See Quickstart for first-run examples.
• Test acceleration (latdx boost then deploy then 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. See Adaptation Lifecycle for the boost / restore / clean / uninstall flow.

The two modes are not mutually exclusive: a workspace can use rapid execution day to day and test acceleration in CI, against the same org.

Configuration scopes

Precedence, highest wins:

1. CLI flag (e.g. --sequential, --no-coverage).
2. Environment variable (e.g. LATDX_LATDB, LATDX_BATCH_MODE, LATDX_ANON_MODE, LATDX_LOG_LEVEL, LATDX_SF_INSTALL_METHOD).
3. User-global config (~/.latdx/config.json, written by latdx config set).
4. Built-in default.

The user-global config file is the only persistent, machine-scoped settings store the CLI manages directly. There is no per-project latdx.config.json written by latdx config; project-scoped overrides are expressed via env vars or per-command flags. CI/release-only env vars are listed separately in the internal env var reference.

latdx config commands

latdx config set <key> <value>   # set a value
latdx config get <key>           # read a value
latdx config list                # print every entry

Supported keys

channel is the only key currently accepted by latdx config set; the canonical schema lives in apps/cli/src/config.ts (CONFIG_SCHEMA). Other ergonomic switches still flow through environment variables; see Environment Variables for the full list.

Test execution engine: sf vs latdx

Use sf for orgs where the standard test runner already works and you only need fast feedback; use latdx (experimental) when you also need the LATdx adaptations (in-memory DB simulation, packed-batch dispatch, per-method coverage). The --db mocked flag only applies to --engine latdx.

Test mode: dbsim vs full

Execution strategy: packed vs sequential

Batch profile: turbo vs eco

Anon-Apex emission: named vs inline

Coverage and Logging Implications

1. Coverage is enabled by default during test run.
2. Use --no-coverage to reduce overhead when coverage output is not required.
3. In org mode, debug log storage limits can block execution; the CLI auto-deletes logs and retries when CI=true or stdout is non-TTY, and prompts otherwise.

Relevant Environment Variables

The most relevant variables for choosing modes:

• LATDX_LATDB (on (default) or off): toggle the LATdx DB simulation runtime. off switches the run to full mode (replaces the former --fullSim flag).
• LATDX_BATCH_MODE (turbo (default) or eco): batch packing strategy for packed execution (replaces the former --eco flag).
• LATDX_ANON_MODE (named (default) or inline): anon-Apex emission strategy (replaces the former --anon-inline flag).
• LATDX_SF_INSTALL_METHOD (SOURCE or MANAGED_PKG): controls latdx-sf install strategy. Defaults to MANAGED_PKG when a managed package id is available (binary builds, or LATDX_SF_PACKAGE_ID is set); otherwise SOURCE so dev checkouts work without an explicit override. Legacy alias SF_PACKAGE_INSTALL_METHOD is still honored with a deprecation warning.
• LATDX_SF_SOURCE_PATH=<path>: pin source-install mode to a specific latdx-sf source root.
• LATDX_LOG_LEVEL and LATDX_LOG_FORMAT: explicit log level / format overrides; see environment-variables.md.
• LATDX_SKIP_TEST_RUNNER_ACCESS=1: skip the auto-deploy/assign of the latdx_TestRunnerAccess permission set.

For the full list of supported environment variables, see environment-variables.md.

Safety Notes

1. Extension runtime has explicit production-org safety behavior by default.
2. CLI docs in this repository do not define an equivalent dedicated production-org guard flag; target sandbox/scratch orgs intentionally.
3. For source-based package install workflows, keep latdx-sf source aligned with required package version expectations.

See also