Setup testing framework vitest #28
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🦋 Changeset detectedLatest commit: 52e7ca4 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Size Change: +26 B (0%) Total Size: 3.61 MB
ℹ️ View Unchanged
|
alexlwn123
force-pushed
the
alex/setup-vitest
branch
3 times, most recently
from
000114b
to
958097f
Compare
alexlwn123
force-pushed
the
alex/setup-vitest
branch
from
958097f
to
b07899f
Compare
alexlwn123
commented
Sep 20, 2024
Comment on lines
+3
to
+4
| // HACK: Fixes vitest browser runner | ||
| globalThis.__vitest_browser_runner__ = { wrapDynamicImport: (foo) => foo() } |
There was a problem hiding this comment.
Not pretty... TODO: open up an issue upstream to report the bug
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Setup vitest for testing library code.
Configuring this properly was tricky. Since the library heavily relies on browser APIs like web workers & wasm, it doesn't really make sense to mock the browser APIs for unit tests. To trust our tests in this library, we really need them to run in a realistic browser environment.
Vitest browser mode + playwright (provider) seems to satisfy all our needs. It spins up a real browser to run tests and can run headlessly for CI. I had to add one hack to make it work with the web-worker, but otherwise it seems to work well out of the box.
This framework should be suitable for all the additional libraries we have planned (e.g. react).