-
Notifications
You must be signed in to change notification settings - Fork 229
Issues: jstemmer/go-junit-report
Need proper handling for invalid character for CDATA field
#138
opened Jul 7, 2022 by
firodj
Open
13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
go-junit-report reports success after failing to compile code
#173
by tzachshabtay
was closed Oct 25, 2023
after I use "go test xxx 2>&1 | go-junit-report > result.xml", then the console doesn't print any more information
#150
by StevenIIV
was closed Nov 25, 2022
go install
of version 'v2.0.0-beta1' fails with "go.mod has post-v2 module path"
#136
by generalmimon
was closed Jul 6, 2022
Parser gojson incompatibility with go test's -coverprofile flag
bug
#134
by forsaken628
was closed Aug 23, 2022
Failure message in the XML report is incomplete from Go 1.14 up
bug
#119
by generalmimon
was closed May 14, 2022
go test
without -v
still gets partially parsed, and returns 0 failures
feature
#109
by nickatsegment
was closed May 14, 2022
Previous Next
ProTip!
What’s not been updated in a month: updated:<2025-04-07.