Amit Saha • 11/6/2021

The "go test" command, os.Stdin and testing interactive input

Read Original

The article details a common issue when testing interactive input in Go: the 'go test' command sets stdin to a null device, causing tests to not wait for user input. It explains the underlying cause by referencing the os/exec package and contrasts behavior with Python. Finally, it provides a practical solution using io.Pipe to simulate and test interactive input scenarios in Go.

0 comments
#testing #golang #Go Test
The "go test" command, os.Stdin and testing interactive input

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
React, useEffect, and Stale Closures: How to Avoid Them with Dependencies and useRef
Jivbcoop • 4 votes
2
Better react-hook-form Smart Form Components
Maarten Hus • 2 votes
3
AGI, ASI, A*I – Do we have all we need to get there?
John D. Cook • 1 votes
4
Quoting Thariq Shihipar
Simon Willison • 1 votes
5
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft • 1 votes
6
Using Browser Apis In React Practical Guide
Jivbcoop • 1 votes