Context
Raised during review of PR #85 (configurable lockfile rebuild).
Problem
The BDD feature files contain no scenarios exercising the lockfile rebuild path introduced in PR #85. The E2E helpers stub cargo::generate-lockfile for fixture correctness, but there is no end-to-end scenario that asserts Cargo.lock files are actually updated after lading bump on a workspace with nested manifests.
Integration tests monkeypatch regenerate_lockfiles rather than exercising the boundary, leaving the complete lockfile rebuild workflow untested at the BDD and E2E layers.
Required work
- Add a BDD scenario (feature file + step definitions) for a workspace with at least one nested
Cargo.toml; assert that the CLI output lists the regenerated lockfiles.
- Add an E2E test that invokes
lading bump on a non-trivial fixture workspace and verifies the Cargo.lock files are present and updated after the run.
References
/cc @leynos
Context
Raised during review of PR #85 (configurable lockfile rebuild).
Problem
The BDD feature files contain no scenarios exercising the lockfile rebuild path introduced in PR #85. The E2E helpers stub
cargo::generate-lockfilefor fixture correctness, but there is no end-to-end scenario that asserts Cargo.lock files are actually updated afterlading bumpon a workspace with nested manifests.Integration tests monkeypatch
regenerate_lockfilesrather than exercising the boundary, leaving the complete lockfile rebuild workflow untested at the BDD and E2E layers.Required work
Cargo.toml; assert that the CLI output lists the regenerated lockfiles.lading bumpon a non-trivial fixture workspace and verifies the Cargo.lock files are present and updated after the run.References
/cc @leynos