Skip to content
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

Status of XML Deserialization in quick-junit #9

Open
nuke-web3 opened this issue Nov 8, 2023 · 2 comments
Open

Status of XML Deserialization in quick-junit #9

nuke-web3 opened this issue Nov 8, 2023 · 2 comments

Comments

@nuke-web3
Copy link

This crate does not currently support deserializing JUnit XML. (PRs are welcome!)

While nextest-rs/nextest#20 is still a work in progress, the JUnit XML format is usable or machine processing. Although, this would be greatly simplified with a (serde compatible ❤️) deserializer crate.

Is there any progress on that front? Sorry if I missed it, I am not able to see any description of the blockers and/or requirements to that being implemented. I would hope this is something of a good first issue that perhaps would not bee too difficult to do 🤞.

@sunshowers
Copy link
Member

Hi @nukemandan --

This was never done. I think someone needs to just put in the work to write a deserializer, and you're definitely welcome to do so.

serde and XML aren't fully compatible sadly, as serde's data model isn't detailed enough. Check out https://docs.rs/quick-xml/latest/quick_xml/de/ for some documentation. That's why I ended up hand-writing the serializer. You're welcome to do it either way though.

@sunshowers sunshowers transferred this issue from nextest-rs/nextest Apr 9, 2024
@sunshowers
Copy link
Member

By the way, nextest can also now produce libtest-like JSON output with an experimental feature: https://nexte.st/book/run-machine-readable.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants