feat: add commands to run tests depending on changed files #1078
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
✅ Deploy Preview for vitest-dev ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
Don't know how to write tests for this :S Maybe by mocking |
antfu
reviewed
Apr 2, 2022
antfu
reviewed
Apr 2, 2022
sheremet-va
commented
Apr 2, 2022
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.
The code for getting files is based on jest implementation, but some of it was removed. Not sure how it will be working, if root and git is not the same? If someone can test in a monorepo, that would be cool. I am ashamed to admit, I am not familiar enough with git terminal commands 👀
I was testing in in
tests/coreby changing code in/srcand it worked fine. So i guess the solution should work for most people, using git.I am getting the changed files and putting it into
relatedarray. Then the logic for related kicks in, and it tries to find tests based on related files. I have a guardif (!related) { // find related }in caserunTestsruns twice (bc of watch mode or else)