[AISOS-2311] Add an end-to-end Forge smoke-test command - #241
Open
forgeSmith-bot wants to merge 1 commit into
Open
[AISOS-2311] Add an end-to-end Forge smoke-test command#241forgeSmith-bot wants to merge 1 commit into
forgeSmith-bot wants to merge 1 commit into
Conversation
Detailed description: - Implemented an end-to-end smoke-test runner under that verifies diagnostic graph execution, workspace/git/podman setup, and container agent run. - Registered the async subcommand and options in . - Added unit tests covering successes, graph failures, missing container system dependencies, agent failures, and cleanup in . - Updated CLI testing documentation in . Closes: AISOS-2311
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.
Summary
This PR introduces a new
forge smoke-testCLI command that verifies a Forge deployment's core runtime path end-to-end without requiring a Jira ticket or modifying remote resources. By executing a diagnostic graph, initializing a temporary workspace, and running a real container agent task, this smoke-test command ensures runtime readiness, service connectivity, and correct configuration.Changes
Core & CLI Implementation
src/forge/smoke_test.py: Implemented a three-stage smoke-test runner that performs diagnostic graph execution, checks container/rootless Podman connectivity, initializes a disposable workspace, and runs a containerized agent to produce and validate diagnostic outputs.src/forge/cli.py: Registered the asyncsmoke-testsubcommand routing torun_smoke_test.Testing & Documentation
tests/unit/test_smoke_test.py: Added five high-coverage unit tests covering successful execution, Stage 1 graph failures, Stage 2 missing container/environment dependencies, Stage 3 execution failures, and cleanup.docs/dev/testing.md: Added CLI usage examples and detailed descriptions of the three verification stages.Implementation Notes
tempfile.TemporaryDirectory. All resources are cleaned up inside afinallyblock to prevent disk bloat.unittest.mockto safely mock environment configurations andContainerRunner.runexecution paths, verifying graceful handling of missing dependencies, stage failures, and cleanup without exposing external secrets or relying on a running container environment.Testing
tests/unit/test_smoke_test.pycovering successful path, stage failures, environment dependency issues, and cleanup behavior.Related Tickets
Generated by Forge SDLC Orchestrator