New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Courtney #645
Comments
I'm actually in the process of sprucing up goconvey right now; Did you know it still has detection for Go 1.2? (not 1.12. 1.2). It also still does manual (incorrect) parsing of I wasn't aware of |
Note to self: https://github.com/dave/courtney So since this accepts regular I don't think we'd want to directly depend on I assume courtney still produces html reports with the same names as |
maybe CLI syntax like |
I'd be perfectly content with just adding a flag in a $ courtney -t="-count=1" -v
$ go tool cover -html=coverage.out -o coverage.html The key point here is that |
FYI, I cloned the return NewCommand(directory, "courtney", "-o", reportPath, "-v") It runs and gives me output. But something odd is going on. The coverage numbers shown in the upper left corner of the web interface look like the non- |
There were some bugs with how goconvey was serving the HTML; I think they may be fixed since you tried this. I'm hoping to spend some more time on goconvey + convey over the holiday break, but I don't know much time I'll actually have :) |
It amazes me that the built in
go test -cover
functionality doesn't support explicitexclusion of code (e.g., error conditions that cannot be reliably triggered). Fortunately,
a tool called
courtney
does support this using special// notest
comments.But
goconvey
uses the standardgo test
mechanism for generating coverage reports. Asa result, I have to run
courtney
separately. This begs the question...would it be possiblefor
goconvey
to use an alternative tool chain to generate coverage? I would guess yes.If somebody could point me to the relevant code and perhaps provide a basic explanation
of how it triggers
go test
, I could consider putting together a PR withcourtney
supportif there is a willingness to accept such a PR.
Or perhaps there is some easy, existing way to change this via existing configuration variables?!?
The text was updated successfully, but these errors were encountered: