Skip to content

test: migrate react tests to vitest #716

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

Open
wants to merge 3 commits into
base: vitest-migration
Choose a base branch
from

Conversation

43081j
Copy link

@43081j 43081j commented Jul 3, 2025

No description provided.

Copy link

changeset-bot bot commented Jul 3, 2025

⚠️ No Changeset found

Latest commit: 0e2f613

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@43081j
Copy link
Author

43081j commented Jul 3, 2025

since we changed a file that the transform tests also depend on, we need to do both in one PR

so this won't build yet until i do that

the transform e2e tests are also a bit wonky. they depend on babel (which only runs in node), but the tests are written as browser tests. in vitest this just errors since babel tries to use things like process

karma will have been bundling and stubbing these out before. it may be that we have to tell vitest to bundle babel somehow

@43081j
Copy link
Author

43081j commented Jul 5, 2025

the tests are intertwined enough that im just going to do the rest in this PR all in one go

so it'll be a somewhat big PR but at least once its done, its all done 👀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant