Re: [go-nuts] Re: rsc.io/script: How to contribute?

github.com/rogpeppe/go-internal/testscript is absolutely wonderful. I've been using it successfully for several years and am the #4 contributor to the project. My only complaint would be that it sometimes takes a few months for changes to be merged and the release cycle is infrequent, meaning t

Re: [go-nuts] Re: rsc.io/script: How to contribute?

On Thu, Mar 7, 2024 at 5:44 AM twp...@gmail.com wrote: > Thanks, but I'm already heavily invested in testscript with over 10K lines > of scripts and a lot of custom configuration, and commander-cli/commander > clearly lacks functionality I need. > OOC, is there anything wrong with github.com/rog

[go-nuts] Re: rsc.io/script: How to contribute?

Thanks, but I'm already heavily invested in testscript with over 10K lines of scripts and a lot of custom configuration, and commander-cli/commander clearly lacks functionality I need. On Thursday, March 7, 2024 at 2:47:03 AM UTC+1 Ajay Kidave wrote: > I have had a good experience using > http

[go-nuts] Re: rsc.io/script: How to contribute?

I have had a good experience using https://github.com/commander-cli/commander for testing CLI commands. It uses a yaml file for test config. I generally avoid yaml but the commander config format is easy to work with. Never used script, the state saving between commands feature might be missing

[go-nuts] Re: rsc.io/script: How to contribute?

*rsc.io/script On Wednesday, March 6, 2024 at 10:46:23 PM UTC+1 twp...@gmail.com wrote: > Internally, Go has a very nice package for integration testing > . > > Roger Peppe has been doing a fantast