Modernize jest-junit CI and local dev setup #273
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
|
@SimenB can you take a look and approve & merge if you agree? I found a new xml parser & validator that will validate all unit tests against the junit xsd. Same behavior we've had the entire project. I needed to force unit tests to run under Jest 30 and utilize node experimental-vm-modules. This change will fix CI for all current and future PRs. |
BartaValentin
approved these changes
Dec 9, 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.
Removes libxmljs and replaces with libxml2-wasm.
Also upgrades jest to 30.0.0-alpha.3 to make use of async setupFilesAfterEnv.