-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Addon Test: Improve error message on missing coverage package #30088
Conversation
const isV8 = e.message?.includes('@vitest/coverage-v8'); | ||
const isIstanbul = e.message?.includes('@vitest/coverage-istanbul'); | ||
|
||
if (e.message?.includes('Error: Failed to load url') && (isIstanbul || isV8)) { | ||
const coveragePackage = isIstanbul ? 'coverage-istanbul' : 'coverage-v8'; | ||
e.message = `Please install the @vitest/${coveragePackage} package to run with coverage`; | ||
} | ||
this.reportFatalError('Failed to change coverage mode', e); | ||
this.reportFatalError('Failed to change coverage configuration', e); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this case would already be handled within the Vitest Manager, so it doesn't make sense to try and handle it here too.
☁️ Nx Cloud ReportCI is running/has finished running commands for commit d51634e. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
2 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile
Closes #
What I did
Changed the error handling for coverage initialisation, to also catch an internal Vitest error that would sometimes be thrown when the coverage package was missing.
It now shows:
Checklist for Contributors
Testing
The changes in this PR are covered in the following automated tests:
Manual testing
This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!
Documentation
MIGRATION.MD
Checklist for Maintainers
When this PR is ready for testing, make sure to add
ci:normal
,ci:merged
orci:daily
GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found incode/lib/cli-storybook/src/sandbox-templates.ts
Make sure this PR contains one of the labels below:
Available labels
bug
: Internal changes that fixes incorrect behavior.maintenance
: User-facing maintenance tasks.dependencies
: Upgrading (sometimes downgrading) dependencies.build
: Internal-facing build tooling & test updates. Will not show up in release changelog.cleanup
: Minor cleanup style change. Will not show up in release changelog.documentation
: Documentation only changes. Will not show up in release changelog.feature request
: Introducing a new feature.BREAKING CHANGE
: Changes that break compatibility in some way with current major version.other
: Changes that don't fit in the above categories.🦋 Canary release
This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the
@storybookjs/core
team here.core team members can create a canary release here or locally with
gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>
Greptile Summary
Based on the provided files and PR information, I'll create a concise summary of the changes:
Improved error handling for missing Vitest coverage packages by adding better detection and more informative error messages.
vitest-manager.ts
test-manager.ts
tovitest-manager.ts
for better organization