Skip to content
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

Specs aren't identified in go test . -json output #639

Closed
jamesrom opened this issue Jan 21, 2020 · 3 comments
Closed

Specs aren't identified in go test . -json output #639

jamesrom opened this issue Jan 21, 2020 · 3 comments
Labels
v2 Issues that will be resolved by v2

Comments

@jamesrom
Copy link

Running go test . -json does not produce usable output when using Ginkgo. To be fully compatible with standard go tooling, producing test events that conform to the test2json spec would be necessary.

In particular, populating the Test field with not just the name of the function that ran the specs, but the name of the specs in the form form "Suite/Context/Spec/Etc".

@ansd
Copy link
Collaborator

ansd commented Jun 30, 2020

Maybe, it's worth to implement a streaming JSON reporter in Ginkgo which would conform with the test2json spec.
A streaming JSON reporter has already been suggested in #143 (comment).

I could give it a try. What do you think @onsi ?

@onsi
Copy link
Owner

onsi commented Apr 5, 2021

I'm going to be implementing the ability to emit a json test report in V2. I'll look into go test's output to see if it's a good fit but i expect i'll be producing a ginkgo specific format.

@onsi onsi added the v2 Issues that will be resolved by v2 label Apr 5, 2021
@onsi
Copy link
Owner

onsi commented Sep 10, 2021

A beta for Ginkgo V2 was just released. It supports emitting JSON-formatted reports though, as mentioned above, it's Ginkgo's own JSON format which includes a bunch of rich test information.

Please try out the beta!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v2 Issues that will be resolved by v2
Projects
None yet
Development

No branches or pull requests

3 participants