-
-
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: Always run Vitest in watch mode internally #29749
Conversation
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 12179c1. 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
Sent 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.
2 file(s) reviewed, 2 comment(s)
Edit PR Review Bot Settings | Greptile
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.
Needs a bit of work, I think.
Package BenchmarksCommit: No significant changes detected, all good. 👏 |
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.
3 file(s) reviewed, 3 comment(s)
Edit PR Review Bot Settings | Greptile
clean: false, | ||
cleanOnRerun: !watchMode, | ||
cleanOnRerun: false, |
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.
style: cleanOnRerun:false could potentially lead to stale coverage data if files are deleted or renamed
expect(createVitest).toHaveBeenCalledTimes(4); | ||
expect(vitest.runFiles).toHaveBeenCalledWith([], true); |
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.
logic: test expects 4 createVitest calls but only verifies empty test run. Should verify both coverage-disabled and coverage-enabled runs
if (payload.config) { | ||
this.handleConfigChange({ | ||
providerId: payload.providerId, | ||
config: payload.config, | ||
}); | ||
} |
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.
style: handleConfigChange is called before checking if the config actually changed, which could trigger unnecessary restarts
What I did
Changed the Vitest logic to always run in watch mode, and then internally disable triggering tests on file changes when SB watch mode is disabled. This ensures that coverage is always re-intrumented on file changes, and Vitest module caches, even when SB watch mode is disabled.
Basically, when we want the flow where we're re-using the Vitest instance, we want to always enable watch mode too, as that is how Vitest expects to behave. Disabled watch-mode are only supported for single-use Vitest instances.
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
Modified Vitest test runner to always operate in watch mode internally while using Storybook's watch mode flag to control test execution, improving cache invalidation and coverage instrumentation.
VitestManager
to always usewatch: true
in Vitest configurationrunAffectedTestsAfterChange
to only trigger tests when Storybook watch mode is enabledcleanOnRerun: false
for coverage options to preserve instrumentation stateTestManager
to handle coverage mode changes without affecting watch mode state