vitest-dev / vitest-dev/vitest
New JSON reporter
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 17.1k
- Forks
- 2k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 94
Description
Clear and concise description of the problem
The current JSON reporter is a jest-compatible reporter made exclusively to support tools that require that format. Vitest doesn't store tests in the same format internally, so it doesn't make sense to expose it that way. We need a separate json reporter.
Suggested solution
- Alias
jsonreporter tojest-json, print a warning if used - Add a new
jsonreporter that uses Vitest tasks
Alternative
No response
Additional context
No response
Validations
- Follow our Code of Conduct
- Read the Contributing Guidelines.
- Read the docs.
- Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing json and jest-json reporter implementations and the surrounding reporter tests. Determine whether the issue should first warn while aliasing json to jest-json, or add a separate reporter based on Vitest tasks; done means the chosen behavior is implemented and covered by reporter tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100