fix: align json output with jest's

[zxch3n]

In the current version(v0.7.11), the JSON reporter's output format deviates from jest's. See Stackblitz example.

In PR #489 json reporter is added, it implements the subset of jest's AggregatedResult type. However, jest --json output is using FormattedTestResults.

And each object in testResults should represents a file rather than a test case.

[netlify]

✅ Deploy Preview for vitest-dev ready!

Name	Link
🔨 Latest commit	86a1b13
🔍 Latest deploy log	https://app.netlify.com/sites/vitest-dev/deploys/62401c231638e7000827a2fc
😎 Deploy Preview	https://deploy-preview-1034--vitest-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[patak-dev]

Thanks for the PR @zxch3n! Things like status being pass instead of passed looks quite important to correct. Interesting that no one noticed this before. I wonder if tools consuming this format are able to accept both.

@cexbrayat would you help us review this PR and check that it won't be a breaking change for your use case?

[cexbrayat]

LGTM, thanks @zxch3n 👍

[krzysztofradomski]

Hey all. Just like to add wanted to weight in from a hmm regular user's perspective ;)
In my current project we've recently switched from jest to vitest, very happy with the change, but the we could not consume the json output in Storybook... So I wrote a simple Storybook addon, which I published to npm just yesterday. This addon of mine depends on the current structure of the output file, and now today I've found this thread haha!

[patak-dev]

Hey all. Just like to add wanted to weight in from a hmm regular user's perspective ;) In my current project we've recently switched from jest to vitest, very happy with the change, but the we could not consume the json output in Storybook... So I wrote a simple Storybook addon, which I published to npm just yesterday. This addon of mine depends on the current structure of the output file, and now today I've found this thread haha!

😬
Well, at least it should be only about removing the addon, no? Have you tried this PR? It would be good to get another confirmation that it is working as expected.

[krzysztofradomski]

Hmm I might give this branch a try later today... Maybe I should just update my addon - I was so proud of it, so not gonna ditch it so fast lol pon., 28 mar 2022, 13:45 użytkownik patak ***@***.***> napisał:

…

***@***.**** approved this pull request. — Reply to this email directly, view it on GitHub <#1034 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC3M4PECKEXENNDUMGPPSVLVCGLWNANCNFSM5RYGN4AA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>