4 ms·
No idea if the technique was original, it’s been too long, but I wrote about it on the Cloudflare blog in 2016. https://blog.cloudflare.com/go-coverage-with-ext
by FiloSottile 4y ago
No idea if the technique was original, it’s been too long, but I wrote about it on the Cloudflare blog in 2016. https://blog.cloudflare.com/go-coverage-with-external-tests/ https://blog.cloudflare.com/go-coverage-with-external-tests/
Anyway, very happy to see the team ship first class support for it. It immediately made coverage support in testscript much more natural, too. https://github.com/rogpeppe/go-internal/pull/201 https://github.com/rogpeppe/go-internal/pull/201
- aleksi 4y agoElastic wrote about that in 2015: https://www.elastic.co/blog/code-coverage-for-your-golang-system-tests https://www.elastic.co/blog/code-coverage-for-your-golang-sy.... I guess multiple people figured it out independently.