Enable Windows PTY interactive tests with go-pty + huh #26
Conversation
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
…rm support Replace creack/pty with aymanbagabas/go-pty to enable cross-platform PTY support including Windows via ConPTY. This change prepares the codebase for PowerShell interactive tests on Windows. Changes: - Updated imports to use github.com/aymanbagabas/go-pty - Changed ptyShell struct to use pty.Pty interface instead of *os.File - Refactored newPtyZsh and newPtyBash to use go-pty API pattern: * Create PTY with pty.New() * Use pty.Command() instead of exec.Command() * Set environment on cmd and start with cmd.Start() - Both zsh and bash interactive tests passing The go-pty library provides a unified interface for Unix PTYs and Windows ConPTY, making it possible to run interactive shell tests on all platforms. Test results: ✅ TestInteractiveCheckoutWithoutArgs (zsh) ✅ TestInteractiveCheckoutWithoutArgsBash 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Add PowerShell interactive and non-interactive tests using the go-pty library. These tests are designed to work cross-platform with ConPTY support on Windows. Changes: - Added newPtyPowerShell() function using go-pty API - Added TestInteractiveCheckoutWithoutArgsPowerShell - Added TestNonInteractiveCheckoutWithArgsPowerShell Current status on macOS: ❌ Both PowerShell tests fail due to upstream PowerShell issue #14932 PowerShell/PowerShell#14932 The issue manifests as: 1. PowerShell parse error when executing shellenv via Invoke-Expression 2. wt function not created (shows as "Application" instead of "Function") 3. No output when sending interactive commands (PTY I/O problem) This is a known PowerShell bug on Unix PTYs unrelated to the PTY library. The go-pty implementation is correct and ready for Windows testing where ConPTY should work properly. Next steps: - Test on Windows with ConPTY support - Consider workarounds for Unix PowerShell PTY issues - May need to skip PowerShell tests on Unix platforms 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
PowerShell has a known bug (#14932) when running in PTY on Unix systems that causes garbled output and I/O hangs. These tests will only run on Windows where ConPTY support should work correctly. Changes: - Added runtime import - Added runtime.GOOS check in both PowerShell test functions - Tests now skip with clear message on macOS/Linux Test results on macOS: ✅ Both PowerShell tests now skip gracefully with message: "Skipping PowerShell PTY test on non-Windows (upstream bug #14932)" References: - PowerShell/PowerShell#14932 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Enable Windows e2e tests in GitHub Actions now that we have PowerShell PTY tests using go-pty with ConPTY support. Changes: - Uncommented and enabled e2e-windows job - Added GitHub App token generation for Windows runner - Configured test matrix for both powershell and pwsh shells - Set up proper test isolation with ISOLATED_TMPDIR - For 'powershell': Run only non-interactive test (legacy Windows PowerShell) - For 'pwsh': Run both interactive and non-interactive tests (PowerShell Core) - Added test log artifact upload on failure The tests will run on windows-latest runner and use go-pty's ConPTY support to properly handle interactive PowerShell sessions. Expected test results: ✅ powershell: TestNonInteractiveCheckoutWithArgsPowerShell ✅ pwsh: Both PowerShell tests should pass on Windows 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Fix two issues preventing PowerShell PTY tests from passing on Windows: 1. **Path separator mismatch**: Removed `filepath.ToSlash()` conversion for TREE_ME_CD marker comparison. Windows outputs backslashes but test was expecting forward slashes, causing false failures even though the command succeeded. 2. **Shell exit timeout**: Changed exit command from "exit\n" to "exit\r\n" (add carriage return) and increased timeout from 2s to 5s to properly handle PowerShell graceful shutdown on Windows. Temporary workflow changes: - Disabled non-Windows CI jobs (test, build, lint, cross-compile, e2e-macos) to speed up iteration on Windows-specific test fixes. Will re-enable once Windows tests pass. Changes: - e2e_interactive_test.go:838: Use native path separator for comparison - e2e_interactive_test.go:264: Send "\r\n" for proper Windows line ending - e2e_interactive_test.go:276: Increase exit timeout to 5 seconds - .github/workflows/ci.yml: Temporarily disable non-Windows jobs with if: false 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit combines two critical fixes to enable Windows PTY interactive tests to pass: 1. **go-pty migration** (from PR #24): - Replace creack/pty with aymanbagabas/go-pty - Add Windows ConPTY support - Enable Windows PTY tests in CI 2. **promptui → huh replacement** (from PR #25): - Replace unmaintained promptui with Charm Bracelet's huh - Fix Windows interactive prompt issues - Enable cross-platform terminal UI ## Problem Statement Windows PTY interactive tests were failing due to two issues: - creack/pty doesn't support Windows (no ConPTY) - promptui has known Windows bugs and doesn't work in ConPTY ## Solution - **go-pty**: Provides Windows ConPTY + Unix PTY support - **huh**: Modern, maintained prompt library with Windows support ## Testing This combined change enables: - ✅ Windows PTY tests infrastructure (go-pty) - ✅ Windows interactive prompts (huh) - ✅ Cross-platform compatibility (macOS, Linux, Windows) ## Dependencies - Added: github.com/aymanbagabas/go-pty v0.2.2 - Added: github.com/charmbracelet/huh v0.8.0 - Removed: github.com/manifoldco/promptui v0.9.0 - Removed: github.com/creack/pty v1.1.24 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Re-enable previously disabled CI jobs that were temporarily turned off during Windows PTY test iteration: - test: Ubuntu tests with Go 1.24 and 1.25 - build: Ubuntu build verification - lint: golangci-lint checks - cross-compile: Build for Linux, macOS (amd64/arm64), Windows - e2e-macos: End-to-end tests on macOS with bash and zsh All platforms should now pass with the combined go-pty + huh solution: - ✅ Ubuntu: Unit tests, build, lint - ✅ macOS: E2E tests with bash/zsh - ✅ Windows: E2E tests with PowerShell/pwsh 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Owner
Author
|
Closing in favor of merged PR #24 |
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 combines two critical fixes to enable Windows PTY interactive tests:
Problem
Windows PTY interactive tests were failing due to two library limitations:
Issue 1: PTY Infrastructure (creack/pty)
creack/ptyis Unix-only, no Windows supportIssue 2: Interactive Prompts (promptui)
promptuiis unmaintained (last commit 2021)Evidence: PR #24 showed non-interactive tests pass, but interactive tests fail with prompt not appearing.
Solution
1. Migrate to go-pty
github.com/aymanbagabas/go-ptysupports both Unix PTY and Windows ConPTYe2e_interactive_test.go2. Replace promptui with huh
github.com/charmbracelet/huh- modern, actively maintainedChanges
Dependencies
Files Modified
main.go: Replaced allpromptui.Selectwithhuh.NewSelecte2e_interactive_test.go: Updated to use go-pty API.github/workflows/ci.yml: Enabled Windows e2e testsgo.mod/go.sum: Updated dependenciesTesting Strategy
CI Tests
The Windows CI workflow tests both shells:
powershell): Non-interactive testpwsh): Both interactive and non-interactive testsTest Coverage
wt co feature-explicit(provides branch name)wt co(prompts for branch selection)Expected Results
With these combined changes, Windows PTY interactive tests should now:
Related PRs
Notes
🤖 Generated with Claude Code
Co-Authored-By: Claude noreply@anthropic.com