29 lines
1.8 KiB
Markdown
29 lines
1.8 KiB
Markdown
# build-test-verification Specification
|
|
|
|
## Purpose
|
|
|
|
Define the runnable local environment and recorded CLI verification result required to close the final MVP build/test verification step.
|
|
|
|
## Requirements
|
|
|
|
### Requirement: Runnable CLI verification environment
|
|
The repository SHALL define step 10 completion in terms of a local environment that can execute the documented `dotnet build` and `dotnet test` commands for `Network.EditMode.Tests.csproj` without failing due to a missing required .NET runtime.
|
|
|
|
#### Scenario: Environment is suitable for verification
|
|
- **WHEN** a maintainer performs the final MVP verification pass
|
|
- **THEN** the environment used for that pass MUST contain the runtime needed to execute the documented CLI build and test commands
|
|
- **AND** the verification record MUST distinguish environment readiness issues from actual build or test failures
|
|
|
|
### Requirement: Build and test commands are re-run and recorded
|
|
The repository SHALL re-run the documented edit-mode CLI verification commands and record the actual outcome for the current MVP networking codebase.
|
|
|
|
#### Scenario: Build and test both succeed
|
|
- **WHEN** `dotnet build Network.EditMode.Tests.csproj -v minimal` succeeds and `dotnet test Network.EditMode.Tests.csproj --no-build -v minimal` succeeds
|
|
- **THEN** project tracking MUST mark the build/test verification step complete
|
|
- **AND** the recorded result MUST state that the edit-mode network test suite passed in the runnable environment
|
|
|
|
#### Scenario: Verification succeeds with warnings
|
|
- **WHEN** the documented build and test commands succeed but emit non-fatal warnings
|
|
- **THEN** the recorded result MUST preserve the warnings as part of the verification summary
|
|
- **AND** the step MUST still be considered complete because the commands passed
|