test(batch): migrate unit tests to Vitest #2938
Merged
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
boring-cyborg
bot
added
automation
boring-cyborg
bot
added
the
batch
dreamorosi
changed the title
sthulb
reviewed
Aug 19, 2024
leandrodamascena
previously approved these changes
Aug 19, 2024
There was a problem hiding this comment.
Hello @dreamorosi! Just small comments that you feel free to accept or not, they have no direct impact on the codebase or the proposal of this PR.
APPROVED!
|
sthulb
approved these changes
Aug 19, 2024
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.
Summary
Changes
This PR migrates the unit tests for the Batch Processing feature to use Vitest.
As part of this work, I have also:
pre-pushgit hook to run tests only on files changed since branching out frommainIssue number: closes #2937
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.