Add JUnit long attribute regression test#2323
Merged
juan-fernandez merged 1 commit intoMay 19, 2026
Merged
Conversation
|
juan-fernandez
marked this pull request as ready for review
May 19, 2026 10:26
Drarig29
approved these changes
May 19, 2026
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
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.
What and why?
Adds a JUnit upload regression test for
[email protected]overflowing on very long XML tag expressions. The dependency bump in #2315 to[email protected]picks up the upstream long tag-expression stack overflow fix discussed in NaturalIntelligence/fast-xml-parser#820, and this keeps the JUnit upload flow covered.How?
Creates a temporary JUnit XML report with a 200k-character
testcaseattribute value, then verifiesgetMatchingJUnitXMLFilesaccepts it as a valid upload payload.Review checklist