Paul Jolly

> My comment was more general. I think the `testscript` package should be a first citizen of Go's tool kit ... somehow. They added fuzzing as `testing.F`, they should consider...

Drive-by comment unrelated to the error you are seeing, @bep: I've not had a particularly enjoyable time trying to test server processes using a command to start the server, and...

> I think Paul means starting and stopping your server program from Go code, via testscript's `Setup` function Exactly so.

> OK, I guess this is a what to be expected on Windows when killing the process (as in, no SIGINT). I will find a workaround, but I'll keep this...

For a fairly involved example I've recently written https://github.com/cue-lang/cuelang.org/blob/a0df30d1ef4858b51bdfe96b7f6c507a0f08fb81/internal/fsnotify/fsnotify_test.go#L57 (which coincidentally might be a package of interest to Hugo).

> * Having test scripts that's self contained and as close to the "real thing" as possible is valuable to me, and I don't mind a little stutter if I...

> I'm a little confused. I see the Setup and the Defer -- but how do you pass arguments from the test script to those? Just to clarify, I'm be...

Updated my latest comment with a link to one of the `.batched` special files to make the point slightly clearer.

At the risk of derailing this bug report still further, just to point out a couple of things: ``` sleep ! stderr . ``` I've found `sleep` to in general...

@fmoralesc - FYI