You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running and enabling coverage in the testing module requires that a coverage provider package is installed. We want to handle this gracefully in multiple ways. The built-in Vitest coverage packages are @vitest/coverage-v8 and @vitest/coverage-istanbul.
During npx storybook add @storybook/experimental-addon-test, we should detect if none of the built-in packages are installed, and ask the user if they want to install @vitest/coverage-v8 (as that is the default) to enable coverage in Storybook.
When running SB, we should detect if the coverage provider package isn't installed. If it isn't disable the Coverage checkbox in the UI with a tooltip explaining why it can't be enabled.
The complexity here is that users can specify 'custom' coverage providers, in which case they don't need any of the two built-in packages installed. we need to handle this case in both 1 and 2.
Running and enabling coverage in the testing module requires that a coverage provider package is installed. We want to handle this gracefully in multiple ways. The built-in Vitest coverage packages are
@vitest/coverage-v8
and@vitest/coverage-istanbul
.npx storybook add @storybook/experimental-addon-test
, we should detect if none of the built-in packages are installed, and ask the user if they want to install@vitest/coverage-v8
(as that is the default) to enable coverage in Storybook.The complexity here is that users can specify
'custom'
coverage providers, in which case they don't need any of the two built-in packages installed. we need to handle this case in both 1 and 2.Original discussion: https://chromaticqa.slack.com/archives/C07AXQABXDZ/p1732659153084449
The text was updated successfully, but these errors were encountered: