Closed jooseppi-luna closed 1 year ago
This should be working without issue. can you confirm that the version of the cli you are using is the same as the version of the library in go.mod? what does ginkgo version
say?
Oh shoot that's what it was! I thought the version of Ginkgo was upgraded with go get but it was still running v1.16.5. Thanks so much for the help and sorry for the bother
hey no worries - glad we could figure it out. more recent versions of ginkgo now warn you when this mismatch occurs so you should have a faster feedback loop going forward.
I just upgraded our e2e testing setup from ginkgo v1.16.5 to v2.11.0, but now there is no output coming from my describe block. Here is an example of what a test run would looked like with ginkgo v1.16.5 (just showing one scenario):
However, now we have lost most of this output and a test run looks like this:
As you can see, there is no output during the test run. We are running the tests using
ginkgo -mod=mod -v
. This is our describe block:Here is a link to our testing setup, if that helps. The e2e.go and e2e_test.go files have most of the ginkgo-related code in them.