Init test infra and first unit test#52
Open
tyulpan wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Vitestis probably the best choice for testing thefrontendof this project.For
e2etesting, we could useplaywright. But that’s for the future.Initialized the standard setup for this.
It looks like the source files in
./src/lib/utils/are the only ones with pure functions and no dependencies (Browser/WASM/Svelte/CodeMirror).I propose starting the coverage there.
output.tsis the best fit for the first one.I propose the following test structure:
unit testsare co-located with the source files they test.tests/directory will be created in the project root, containing:integration/: forintegration testse2e/: forend-to-end testsRelated to #19.