test: distinguish unit, integration and e2e tests#291
Merged
Conversation
Tlacenka
force-pushed
the
unit-integration-e2e-setup
branch
from
0c3eb70 to
910a4be
Compare
Tlacenka
force-pushed
the
unit-integration-e2e-setup
branch
from
31e4857 to
a0a87fc
Compare
matejchalk
approved these changes
Nov 20, 2023
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
2 participants
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.
Closes #263
In this PR, I did the following:
testtarget for unit and integration tests - the new test file format is.unit.test.ts,.integration.test.tsand.e2e.test.ts.testing-utils, I do not expect any integration or E2E tests so I only set up unit tests.vitestconfig for different types of tests.nxtargets and included all duplicate options innx.json.I split the commits based on area or package for an easier review.