The post dives into the evolution of how the Go team tests the 'go' tool, focusing on different strategies for testing CLI tools. It covers the transition from using a bash script ('test.bash') to 'testgo' in Go, and finally to a more advanced 'script_test.go'. The post introduces 'testscript', a package that allows for testing

16m read timeFrom atlasgo.io
Post cover image
Table of contents
Introduction ​CLIs and Go ​Motivation ​Testing CLI tools ​How the Go team tests go test ​Introducing testscript ​Personal impact ​Conclusion ​
1 Comment

Sort: