-
Notifications
You must be signed in to change notification settings - Fork 9
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
Junit format system-out
is missing for testcase
but added only for testsuite
#130
Comments
Just reallized there was a PR on the old repo : https://github.com/spekt/junit.testlogger/pull/47/files Perhaps it could be revived here |
@jonesbusy thanks for reporting this issue. We definitely want to support reporting attachments for junit. Would you be interested to contribute/port the above PR to this repo? |
I can try but for the moment I'm struggling to run acceptance tests on my environment (.NET 8.0 / WSL2) I'm not familiar with .NET environment I don't know what was decided at the end, but my idea would be simple for the moment Update the xsd schema by allowing |
I haven't tried building this repo in WSL2. What's the error?
The approach looks good to me. |
Fixed with dff18d6 |
Thanks! I didn't had time to take a look at it, but it's a good christmas present 🎅🏼 |
Great, thanks for confirming. Happy holidays! |
Hi,
First of all thanks for this great project, it's super useful.
I'm running
nunit
andjunit
logger because I need both format to be imported on 3rd party tool.When looking at the
nunit-results.xml
everything is correct.The test only output
But when looking at
junit-results.xml
thesystem-out
is not linked to the test case but the test suite. And it contains irelevant information. Additionnally the CDATA is missingI would expect to see something like
I have compared with other junit format and the
system-out
is well supported fortestcase
blockFor example
dotnet test --settings:ui.runsettings.
Expected behavior
A clear and concise description of what you expected to happen.
Other details
dotnet test --diag:log.txt
On don't think there is anything useful there, but I can provide if neededThanks
The text was updated successfully, but these errors were encountered: