Add clarification for xunit reporter format

DevExpress / testcafe-reporter-xunit

This is the xUnit reporter plugin for TestCafe.

https://testcafe.io

MIT License

9 stars 30 forks source link

Add clarification for xunit reporter format #5

Closed chrish619 closed 1 year ago

chrish619 commented 5 years ago

Issue: Documentation

Steps to Replicate:

being silly, and not understanding there's a difference between XUnit, and a xUnit.Net format (@chrish619)
Add a "Publish Test Result" step to Azure DevOps / vsts CI Build - setting XUnit as the source format - (but really this means xUnit.Net format)
Total test results: 0. logged in system.debug build log

Possible resolutions?

Read documentation better - @chrish619
Please add a small FAQ, N.B., or 'Gotcha' to the readme.md - to prevent other developer confusion?
An Azure DevOps/VSTS integration guide, and mention the JUnit format as being a solution?

Or, maybe this "Issue" will be enough 😄

AndreyBelym commented 5 years ago

Thank you for your feedback. Yes, there is a subtle difference between different meanings of the xunit word: the xUnit family of formats derived from the JUnit format and the specific xUnit.net format. This plugin uses the first meaning of xunit. I think we should add a clarification about this in README.md.

agentHoover commented 5 years ago

Any chance you are planning to add support for the xunit.net format? That would be more helpful than just documenting that it is not supported. :)

AndreyBelym commented 5 years ago

@agentHoover it requires more works that just documenting that Xunit.net is not supported by this reporter. By the way, if we implement Xunit.net support, we will create a separate package to preserve backward compatibility. So if you write a Xunit.net reporter, we can consider using your implementation and promote it in the Plugins section in the TestCafe documentation :smile:

github-actions[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had any activity for a long period. It will be closed and archived if no further activity occurs. However, we may return to this issue in the future. If it still affects you or you have any additional information regarding it, please leave a comment and we will keep it open.

github-actions[bot] commented 1 year ago

We're closing this issue after a prolonged period of inactivity. If it still affects you, please add a comment to this issue with up-to-date information. Thank you.