-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
subunit support #34
Comments
I'm glad you are liking green! Tell your friends about it ;-) I have never used subunit before. Is it this project on launchpad? There is already an html option, but that's not really structured. Just marked up. And honestly I didn't end up using the html output option and it's a pain to maintain, so I was considering removing it. Perhaps a json output option in its place would make sense. That may be better than trying to directly interface with every possible expected input. Then people could present the data however they wanted. |
Yes. And python-subunit on PyPI. I'm not sure if junit-xml or subunit has more support, but I suspect the former ;) |
You can (easily) downconvert subunit to junit XML -- and it's fairly easy to generate subunit if you have similar support for reporters as trial does (I haven't checked, is there?) Regardless, if you have subunit support you'd be able to use green in Jenkins. |
@Julian Green does not have a plugin interface like trial reporters, and I have no plans to add one at the moment. I do still think it would be good to add features to green such as subunit support, though. Real life just keeps delaying me from getting to it. Patches welcome if someone beats me to it! |
I've just started playing with Green and it works really well so far. However, I'd like to use it in automated tools, and I've had good success with subunit for this (reporting up to buildbot, for example).
Supporting subunit via a plugin or directly would be great!
Alternatively, some sort of structured output option (junit XML? json?) would be nice instead (or as well).
The text was updated successfully, but these errors were encountered: