-
Notifications
You must be signed in to change notification settings - Fork 71
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
Feature: xunit/junit output #50
Comments
@Puciek let me finish with the I'll ping you once that's done, implementing your choice of output should then be much easier. 😄 |
@bbqsrc oh, aces, will do! Got any sort of ETA? Just so I can plan accordingly :) |
Yeah, within a week or so. There's no longer an output trait but instead an event handler callback function, so you basically only need to have a function that takes a single I don't anticipate those events changing very much, so I'd be quite happy for you to have at least a look at the branch as it currently stands as the more feedback the better, imho. 😄 |
I'll dig in! Thanks! |
Hey @Puciek, just checking in. Have you made any progress? Hit any roadblocks? I'd welcome the feedback. Also if you have any documentation about the xunit or junit output formats, I'd appreciate some links. I'm not really able to find anything so far and it's frustrating me haha |
@bbqsrc I will have an update for you over the weekend (this one), as I was hopelessly stuck this week, sudden surge of unexpected work :) As for docs, xunit: https://xunit.net/docs/format-xml-v2 There are very common across loads of technology, very much the standard for test reporting (and integrated into majority of IDEs as a result). |
@Puciek no problem 😄 On the branch Ping me if you get stuck, I'll be around. |
And now I've merged those output changes into |
@bbqsrc I finally got the ball rolling with it, and gotta say I love the new format you've setup for output handling, makes is a breeze (once you figure it out ha!). I should have a draft PR ready by end of this week with it, depending just how busy the last few days will be at work. |
@Puciek wonderful! thanks! |
Hey @Puciek, just checking in! Things still progressing? |
@bbqsrc Yep, just mostly work is going on in the underlying library. Should be able to wrap this up soon™ |
I look forward to reviewing your PR soon™, 😄 |
@Puciek 0.7.0 has been published now. 🎆 |
@bbqsrc Time bloody flies doesn't it? In last month i literally only had one hour to do OS stuff :/. But I've set time for this weekend and will bloody finish this, as it's embarrassing, and I apologize that this went from making headway to being dead, even more so that I still need it myself hah! |
No problem, took me long enough to get the develop branch merged back into master as it is. 😄 Take your time and don't burn out, it's a voluntary effort. |
I'm very interested in this feature or something similar. As it stands, integration tests which use Perhaps, use If there's anything you can point me to that shows this I'd appreciate it. Would think that adding a formatter for the Cucumber |
It looks like @Puciek started on this at https://github.com/Puciek/cucumber-rust/commits/feature/junit-output so that may be a good starting place |
- impl `writer::JUnit` behind `output-junit` Cargo feature - make `writer::Basic` generic over `io::Write` implementor Co-authored-by: Kai Ren <[email protected]>
I believe that adding j/xunit output support would go a long way to streamlining the tests, as those are the formats supported by IDE's and CI tools, so it would make cucumber-rust fit in like a glove with how devs work right now, rather than relying on reading the text output.
I will probably give it a whack myself, as it's of high interest to me, but certainly, welcome any pointers and suggestions!
The text was updated successfully, but these errors were encountered: