Build command boundary tests
Section titled “Build command boundary tests”Inno.Build.Cli.Tests checks the public Build command entry. These integration tests own command admission and routing, so a simple command regression does not need the product integration suite merely to reach the CLI.
Behavior covered
Section titled “Behavior covered”- Invalid commands fail before SDK discovery or cache cleanup.
- Prior cancellation creates no build state or authoring workspace.
- Invalid explicit source and SDK selection fail before taking checkout ownership or creating project state.
- Architecture verification reaches the public validator without preparing a product.
- Native verification rejects a target without an Editor runner before creating state.
- Script export and IDE projection use managed authoring without requiring native source or a tools target.
Script fixtures also include an unrelated broken product cache: managed authoring must not sweep that cache as a side effect of compiling scripts. Script cancellation retains its own workspace and publication rules.
Run and maintain
Section titled “Run and maintain”Use the shared validation workflow. A focused CLI diagnostic is:
dotnet test tests/build/Inno.Build.Cli.Tests/Inno.Build.Cli.Tests.csproj --configuration Debug --disable-build-servers -m:1 -nodeReuse:falseSDK selection and real script compilation require the declared SDK. Early argument-rejection cases must remain early; do not add product preparation to make their fixtures pass. No product or raw-binding API coverage is implied by these command tests.
Browse the pinned command fixtures. Follow suite maintenance when extending command behavior.