ut.hpp: Corrected XML formatting issue in print_junit_summary #621
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
Previously, an empty element tag was erroneously used in place of an opening XML tag within the print_junit_summary function. This resulted in the generation of invalid XML output. The issue has been resolved by replacing the empty element tag with the appropriate opening XML tag, ensuring the XML output adheres to the expected format.
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.
Previously, an empty element tag was erroneously used in place of an opening XML tag within the print_junit_summary function. This resulted in the generation of invalid XML output. The issue has been resolved by replacing the empty element tag with the appropriate opening XML tag, ensuring the XML output adheres to the expected format.
Problem:
Invalid XML generation
Solution:
Use opening XML tag in place of an empty element tag
Issue:
#567 Fixes invalid XML issue. Still doesn't conform to JUnit
Reviewers:
@krzysztof-jusiak