Fix test capturing stdout when version output moved to stderr #12750
+2
−1
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.
PR #12704 routed version command output to stderr (diagnostic output convention), breaking
TestMainFunctionExecutionPath/main_function_basic_execution_flowwhich usedcmd.Output()to capture only stdout.Changes
cmd.CombinedOutput()to capture both stdout and stderrThis aligns with the pattern used in other integration tests (e.g.,
pkg/cli/completion_integration_test.go) for commands that may output to either stream.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.