This is a tracking issue for the Project Coverage 🛡️ project. The purpose of this issue is to keep tracking of the overall status of the project and tasks, and plan everything around it. This project is a continuation of #29088 and is related to #29529 and #29531.
⚠️ Problem
It's not immediately clear how much of a project's UI is covered by tests/stories. Storybook can provide that via Vitest's coverage report.
🏁 Goals
Users are able to view project coverage in Storybook.
User should be able to view project test coverage % inside storybook. The coverage % should update every time user does a complete test runs.
User should also be able to view the overall project coverage percentage within storybook, and clicking on the coverage takes you to the Vitest coverage report.
Project coverage should respect the Vitest coverage config.
Document how to use this and integrate with coverage tools, CodeCov, etc.
🚩 Milestones
## Main milestone
- [ ] Add Coverage line to Testing Module UI
- [ ] Enable coverage in Vitest runs when coverage event is sent
- [ ] Respect user's coverage config in their Vitest config
- [ ] Display coverage percentage in Testing Module UI
- [ ] Create page with Vitest's HTML-based coverage report
- [ ] What about nycrc?
🧑🤝🧑 Who: @JReinhold, @ndelangen and @ghengeveld
This is a tracking issue for the Project Coverage 🛡️ project. The purpose of this issue is to keep tracking of the overall status of the project and tasks, and plan everything around it. This project is a continuation of #29088 and is related to #29529 and #29531.
⚠️ Problem
It's not immediately clear how much of a project's UI is covered by tests/stories. Storybook can provide that via Vitest's coverage report.
🏁 Goals
Users are able to view project coverage in Storybook.
🚩 Milestones