Configuration and Modes (CLI)

Execution Modes

Test mode: `dbsim` vs `full`

Mode	How to select	Characteristics
`dbsim` (default)	default behavior	Optimized simulation path; enables packed/concurrent execution strategies where eligible.
`full`	`--fullSim`	Uses full simulation path with more traditional execution semantics.

Execution strategy: `packed` vs `sequential`

Strategy	How to select	Characteristics
`packed` (default)	default behavior	Batch-oriented execution, best for throughput in org mode.
`sequential`	`--sequential`	Easier debugging/isolation, lower throughput.

Batch profile: `turbo` vs `eco`

Profile	How to select	Characteristics
`turbo` (default)	default behavior	Prioritizes parallelization and faster completion.
`eco`	`--eco`	Reduces worker pressure, prioritizes efficiency/stability.

Coverage and Logging Implications

Coverage is enabled by default during test run.
Use --no-coverage to reduce overhead when coverage output is not required.
In org mode, debug log storage limits can block execution; CLI can prompt for cleanup and retry.

Relevant Environment Variables

The most relevant variables for choosing modes:

LATDX_SF_INSTALL_METHOD (SOURCE or MANAGED_PKG): controls latdx-sf install strategy. 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.

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

Safety Notes

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

CLI Reference Troubleshooting