Child-process execution tests
Section titled “Child-process execution tests”Inno.Testing.Processes.Tests validates NativeProcessTestHost.Run through its public contract. Its embedded executable fixture is test infrastructure, not another daily engine entry point. These scenarios do not need BGCS, a GPU or a native product.
Behavior covered
Section titled “Behavior covered”- Successful exit drains both standard output and standard error completely.
- Nonzero exit retains both streams, the command and the contract identity.
- Timeout preserves partial output and terminates descendants.
- Relative assembly paths and invalid execution budgets are rejected.
Run and maintain
Section titled “Run and maintain”Use the shared validation plan. A focused process-host diagnostic is:
dotnet test tests/process/Inno.Testing.Processes.Tests/Inno.Testing.Processes.Tests.csproj --configuration Release --disable-build-servers -m:1 -nodeReuse:falseThe machine must permit local process creation and testhost communication. Fixtures own and drain their child processes; cancellation must not leave descendants running. Follow suite maintenance. The reusable process-host library retains its own public API obligations even though these discovery classes are not product APIs.
Browse the pinned project and scenarios. This reference describes available assertions, not current-run certification.