Repository navigation
test: replace process-exit smoke test with HTTP assertions - #12
Merged
Merged
Conversation
WilliamRagstad
marked this pull request as ready for review
October 25, 2026 22:16
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The runtime smoke test slept and exited the entire test process without verifying a response. Replace it with real loopback HTTP requests that assert HTML, headers, 404s, static files, and handler errors. Tests use ephemeral ports, temporary projects, explicit runtime shutdown, and joined workers; disconnected clients no longer panic the runtime.
This is PR 1 of 4: HTTP harness → routing → reload → runtime isolation and todo example. CI now runs on main and stacked PRs with locked dependencies.
Validation:
cargo test --locked— 2 passed. Request deadlines indicate failures only; they are never success criteria.