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

[Tracking]: Project Coverage πŸ›‘οΈ #29530

Open
6 tasks
JReinhold opened this issue Nov 4, 2024 · 0 comments
Open
6 tasks

[Tracking]: Project Coverage πŸ›‘οΈ #29530

JReinhold opened this issue Nov 4, 2024 · 0 comments

Comments

@JReinhold
Copy link
Contributor

JReinhold commented Nov 4, 2024

πŸ§‘β€πŸ€β€πŸ§‘ 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

  1. Users are able to view project coverage in Storybook.

    1. User should be able to view project test coverage % inside storybook. The coverage % should update every time user does a complete test runs.
    2. 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.
    3. Project coverage should respect the Vitest coverage config.
  2. Document how to use this and integrate with coverage tools, CodeCov, etc.

Image

🚩 Milestones

Main milestone

@JReinhold JReinhold changed the title [Tracking]: Project Coverage [Tracking]: Project Coverage πŸ›‘οΈ Nov 5, 2024
@shilman shilman moved this to In Progress in Storybook Roadmap Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Under Consideration
Development

No branches or pull requests

3 participants