How to pass arguments to ginkgo if I run go test?

[ryan-ju]

I can't figure out how to pass -v or -trace arguments to ginkgo if I run my test as go test.

Is this supported?

[iandelahorne]

-ginkgo.v and -ginkgo.trace, respectively.

[williammartin]

@ryan-ju Looks like this is closeable now. If you have any further questions please feel free to reopen.

Thanks @lflux for the response.

[anandsinghkunwar]

This doesn't work.

go test ./e2e -ginkgo.v -ginkgo.progress

But this works,

cd e2e
go test -ginkgo.v -ginkgo.progress

@iandelahorne Do you have any idea why this might be?

[williammartin]

Have you tried:

go test -ginkgo.v -ginkgo.progress ./e2e

[anandsinghkunwar]

Yes, I get can't load package error

[williammartin]

Right, I think I was a little confused by your "doesn't work" in your first comment.

→ go test ./scratchpad -ginkgo.v

→ ps aux | grep test
...
pivotal          18443   0.0  0.0  4385664   8916 s010  S+   12:57pm   0:00.01 /var/folders/sr/40vc_pv552v9ggy1_fvb3zdw0000gn/T/go-build224624199/b001/scratchpad.test -ginkgo.v

We can see here that the ginkgo.v argument is passed to the test binary.

I suspect what you are saying is "I don't get verbose output". When you run go test in package list mode i.e. go test <pkg> OR even go test . the test runner turns down the verbosity in comparison to local directory mode i.e. go test.

As such, I suspect the command you are looking to run is:

go test ./e2e -ginkgo.v -ginkgo.progress -test.v

Let me know if this works for you

[anandsinghkunwar]

@williammartin This works! Thanks a ton, I always thought this was a ginkgo bug but never checked the ps aux output to verify. I just assumed it was related to ordering and flag parsing and a corner case that wasn't handled. Glad to know it was a user error. :)

[williammartin]

Neat, no worries, it's a bit confusing behaviour that you need to pass two verbose flags.