I'm so glad to hear it helped you!
> I wonder where the blog author found that flag? It's not exposed in `go
test`
I guess "-test.gocoverdir" parameter is not exposed to go test users well.
There is an another comment that it was very hard to find documents about
"-test.gocoverdir" parameter.
Oh that's perfect! Pretty much what I was looking for. Let me test it and
get back to you.
I wonder where the blog author found that flag? It's not exposed in `go
test`
On Tuesday, January 14, 2025 at 5:27:07 AM UTC-8 Byungjun You wrote:
> Have you try go test with -args -test.gocoverdir param
Have you try go test with -args -test.gocoverdir parameters?
> go test -cover ./... -args -test.gocoverdir="{a directory where coverage
reports should be generated}"
I found this blog post is very helpful when merging unit and integration
test coverage reports.
https://dustinspecker.com/posts/g
The blog post doesn't provide a way to translate the output of `go test
-coverprofile ...` (which is the so-called legacy text format) into the new
binary format, which `go tool covdata merge` expects. It only provides it
in the reverse, i.e. the new binary format to the legacy format. So it
me
On Sat, Jan 11, 2025 at 10:07 AM Paul Chesnais (papacharlie)
wrote:
>
> Is there another forum I can ask about this? Should this be a feature request
> against the go team directly? It seems strange that the formats haven't been
> converged, or that there's no way to get the new binary format fr
Is there another forum I can ask about this? Should this be a feature
request against the go team directly? It seems strange that the formats
haven't been converged, or that there's no way to get the new binary format
from `go test`
Cheers,
Paul
On Tuesday, December 3, 2024 at 1:26:04 PM UTC-
