jUnit XML-Like Output about shunit2 HOT 21 OPEN

I would really like to get the xml format support into shunit2. What is needed 
to get
this integrated into shunit? Make it optional? Allow to specify the output 
style?

Currently the proposed patch is a partial rewrite of the existing code. It was 
done
for a personal homework. So you have to understand that it is is not fully 
tested,
and is rather intrusive: xml is the default format. Right now, I do not have 
enough
time to update this code, but there should not be too much work to make the xml
output optional. Nonetheless, I am very interesting by a,y feedback. We keep in
touch! Thanks for your comment ;-)

Hi Frederic, thankyou for posting this patch. This is really useful.

the junit-xml patch works great! Now I'm merging Kate's new changes in to the 
patched r294.

Ok, I've got a patch that updates 2.1.6 to include Frédéric Moulin's 
JUnit-xml patch.  Unfortunately it is not too clean - it reduces shunit2 to 
only work with bash, and I've only been able to test it on Ubuntu and Redhat 
linux flavours.  With some more cleanup it can be made available.  Contact me 
for the dirty patch - however, I endavour to come up with a proper patch that 
allows for both the junit-xml output and the normal shunit2 output.

In fact anyone else is in my position, I'm hooking the tests up to Atlassian 
Bamboo's test reporting.  So if that happens to be what you're doing, then I 
suspect my dirty patch might be just the ticket for you!

Regards,
-Ben

Ben - Would like to get your patch for JUnit XML output in 2.1.6.  Please post, 
if possible.  Much thanks!

Same here ! I would be really interested by the patched version with XML output.

This hasn't been merged yet?

Attached! There was quite a bit of tweaky stuff,
but in the end I did manage to merge 2.1.6 with the earlier work that
another fellow did to get junit-xml with an earlier version of shunt.
The patch is a bit messy, but it works great for us. We are now using
this approach with quite a few of our products.

Here's my diff command:

diff -u -r shunit2-2.1.6-orig shunit2-2.1.6 > shunit-2.1.6-xml.patch

Enjoy!

Bummer! Only bash?! That not good :\

I'm sure it could be made to work without bash, but that was not in my 
requirements so I took the shortcut and just used bash.

Here's a, so far working, non bash dependent, patched, version of shunit2:
    https://github.com/s0undt3ch/shunit2

The regular output was kept, but can be omitted using SHUNIT_STDOUT.
There's an option to include the environment or not using SHUNIT_INCLUDE_ENV.

Could we get this patch included in the official shunit2 along with a new 
release ? 
Or is this project not supported anymore ? 

Thank you

[deleted comment]

It seems that s0undt3ch is no longer supporting the XML patches

https://github.com/s0undt3ch/shunit2/pull/1

I have forked and fixed a couple of issues.

https://github.com/jeremycarroll/shunit2

My interest in the xml output is for integration with jenkins, and our 
continuous test server.

Thanks. This is a good thing, I've been needing this for a while. We've had to 
kludge JUnit XML output via a Perl script that runs with the end-of-suite hook. 
Our goal is also to integrate with Jenkins.

Thank you very much !
My question about support was more related with the project in itself. Ideally 
the fork should be merged back with the original shunit2 and released. 

Thank you again, I will use it with Jenkins. 
Barth

Hi Jeremy, 

I have also started to correct the XML patches to make it work with jenkins. I 
haven't had time to check your version, but you might want to check my patches, 
some of them might be useful: 
https://github.com/fekete-robert/shunit2/commits/jenkins

(I am not a programmer, so they might be ugly as hell.)

Regards, 

Robert

Hi, 

I think that we should change the line
    cat << EOF >> "${SHUNIT_OUTPUTDIR}/TEST-${__shunit_suite_name}.xml"
into
    cat << EOF > "${SHUNIT_OUTPUTDIR}/TEST-${__shunit_suite_name}.xml"

Appending only results in an invalid xml file. 

Hi, 

in the patch the functions oneTimeTearDown and oneTimeSetUp must not be piped. 
That is important in order allow the called code to modify variables such as 
the suite name.

Cheers,
Barth