I reopened an old bug for this, and perhaps it will get some attention. https://github.com/golang/go/issues/6623
On Sunday, January 12, 2020 at 1:19:59 AM UTC-5 Fazlul Shahriar wrote: > I also wrote a tool like that: https://github.com/fhs/golinecov > It displays coverage report from 'go test' without any color or fancy HTML. > I wrote it because I wanted something text oriented that I can view within > my editor. > Hope it's useful. > > fhs > > > On Saturday, January 11, 2020 at 1:41:01 AM UTC-5, andrew...@elastic.co > wrote: >> >> On Thursday, January 9, 2020 at 11:39:41 PM UTC+8, Jared Stofflett wrote: >>> >>> I'm a totally blind developer who is trying to learn go. When running >>> >>> go tool cover -html=cover.out -o cover.html >>> >>> It appears the HTML generated uses color to show the lines of code that >>> are not covered without any other way of identifying uncovered lines. This >>> is obviously an issue if your totally blind. Are there any alternative >>> tools that can take a coverage profile and give a text representation of >>> lines that are not covered? >>> >> >> A long time ago I wrote a tool that will annotate source code with >> coverage, generating plain text output. Lines that are not covered will be >> annotated with "MISS". I don't know how well this will work for you, but >> you could give it a try. You can find it here: >> https://github.com/axw/gocov >> >> You can annotate the source of the package in your current working >> directory by running "gocov test | gocov annotate -". The hyphen at the end >> is necessary to read from stdin. >> >> Hope this helps. >> >> Cheers, >> Andrew >> > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/5552940d-eb27-49f4-a017-b35a54f3a489%40googlegroups.com.
