Hello. Recently I've wrote a small (hacky) package so that I could easily spin up a Go server I was writing right from within its tests.
I often find the need to write some end-to-end tests for a main package (usually some kind of server) and to do that I want to spin the actual binary, so that I test the full flow as much as possible. Doing this involved much boilerplate code, so I thought other people could benefit from this too. To get an idea what this feels like, refer to this example: https://github.com/agis/spawn/tree/master/examples I'd love to hear thoughts and feedback. Cheers. P.S. https://github.com/agis/spawn -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
