Hi all, I've been wanting for some time to have coverage instrumented programs: gather coverage data not only from running unit-tests but also from running multiple runs of the final program and testing it behaves as expected. That seems to be an easy way to cover some ground without having to mock the world, while keeping unit-tests for finer details. Both have their use I believe.
I couldn't find many people doing this kind of things, so I ended up hacking something that works for me™. More details can be found in a blog post (it's rather long): http://damien.lespiau.name/2017/05/building-and-using-coverage.html and its companion repository: https://github.com/dlespiau/covertool I may have missed something not-so-obvious. Feedback is obviously welcomed. If I haven't missed something, It'd be nice to have this kind of thing better integrated with the go tool chain. -- Damien -- 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.
