-
Notifications
You must be signed in to change notification settings - Fork 8
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
Output Junit file doesn't have test name for a test case #7
Comments
Hey @RohitVegesna could you please attach the |
Hey @gabrielweyer, Please let me know if you require any more info to troubleshoot the issue. Thanks |
I assume you provided a value to [Fact(DisplayName = "Ignoring scenario")] I published v3.0.0 on NuGet moments ago. Please let me know if it doesn't solve your issue. |
@gabrielweyer With the new version. I am able to see the name in the converted file. |
Hey,
Thanks for developing this nice tool which helps in uploading test results in CircleCI.
We tried to use this package and upload test results in circleCI run but looks like we have no test case name shown both in ran pipeline and circleCI insights. When looking further into resulted JUnit file, found that there is a test case name printed which we have in the source file (xunit result).
Attaching our sample snipptes of both xunit_result.xml and junit_result.xml (which was generated using this nuget)
![image](https://user-images.githubusercontent.com/75778145/140911791-754305d7-28e6-42e2-9f5c-bb77321296bc.png)
Snippet of Xunit_result.xml
Snippet of resulting file (junit)
![image](https://user-images.githubusercontent.com/75778145/140911852-0dd06a6a-3b08-48a7-8542-7382d4e68095.png)
In the above snippet, test case name is blank.
We are using 'XunitXml.TestLogger' nuget to generate the xunit result XML.
Could you please guide us on how to resolve this, without the test name in the JUnit file, circleCI shows blank rows under the test case name column.
Your response is highly appreciated !!
Thanks in advance.
The text was updated successfully, but these errors were encountered: