cargo test --workspaceThe main CLI integration tests live in:
crates/avm-cli/tests/cli_scenarios.rs
They cover:
- local alias resolution
- local/global precedence
- Node
package.jsonscript discovery - plugin-first command routing with
avm node ... - shim fallback when a managed Node version is missing
Run the complete isolated test suite:
docker/tests/run-docker-tests.shThis runs:
cargo test --workspace- scenario shell tests under
docker/tests/scenarios/
Run one scenario:
docker/tests/run-docker-tests.sh 01
docker/tests/run-docker-tests.sh 03-shim-fallback.sh| Scenario | Purpose |
|---|---|
01-basic-alias.sh |
Alias run, resolve, source, and env export. |
02-local-global-precedence.sh |
Local override and global fallback behavior. |
03-shim-fallback.sh |
Missing managed Node version warning and system fallback. |
04-node-package-scripts.sh |
Node provider script aliases and lockfile manager detection. |
The CI workflow should run:
cargo build --workspace
cargo test --workspace
bash scripts/check-changelog.shBefore enforcing format or clippy as blocking release gates, run and normalize:
cargo fmt
cargo clippy --workspace --all-targets