CUNIT compliant for Jenkins and comments are possible #2
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
CU_LOG to add logging for Cunit. This is put in the comment for JUNIT XML output.
Add normal text logging (CU_LOG) to Junit XML
Add normal text log to CUNIT
Add default logging to XML JUNIT files. Use CU_LOG
Add myself
Add example to test
Example for Jenkins output test
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fork extended with comments in JUNIT file.
Now CUNIT is really compliant with Jenkins and Junit tests
Small improvements for wildcards and more readable XML output.
Summary report improved at end of running.