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

jUnit XML-Like Output #16

Open
GoogleCodeExporter opened this issue Jun 26, 2015 · 27 comments
Open

jUnit XML-Like Output #16

GoogleCodeExporter opened this issue Jun 26, 2015 · 27 comments

Comments

@GoogleCodeExporter
Copy link

Hello,

I would like to submit you a bunch of changes:
  - adds a trick to prevent tested scripts to prematurely exit,
  - fixes a typo in docbookPrep.sh,
  - translates output report format to jUnit XML format,
  - adds a command to run all test suites in a directory and optionally
write test reports to a specific directory (shunit2_testsuite),
  - adds a command to join all test suite reports in a directory into a
single one report (shunit2_collect).
  - adds a RPM specfile.

The API was not changed at all. And by default, reports are displayed to
stdout except if the SHUNIT_OUTPUTDIR is set. In that situation, the report
is saved to $SHUNIT_OUTPUTDIR/TEST-<test suite name>.xml, eg
/tmp/testsuites/reports/TEST-foo.xml for test suite foo.sh.

Please note, that due to network issues, I was not able to start coding
from the latest version (r294) but instead I started from the latest stable
release ie 2.1.5.

Nonetheless, I let you assess the pertinence of those changes and let you
pick whatever is needed to the project. Please help yourself!

Regards,

Frédéric MOULIN.

Original issue reported on code.google.com by [email protected] on 23 Oct 2009 at 7:02

Attachments:

@makefu
Copy link

makefu commented Nov 20, 2018

Hey, i know it's been almost 5 years but i wanted to ask what the status if this issue is.
Is there a way to get the patch integrated?

Also, i've seen there is a fork which already implements the feature:
https://bitbucket.org/eddiewebb/shunit-with-reports

Regards!

@JussiPekonen
Copy link

Now that I have used this tool a bit more, I was kind hoping to have this feature available. I see that there have been attempts to get this done, but those are now outdated as their implementation is based on old version of this repo.

If there is still demand for this, I can try to give it a try.

@AJIOB
Copy link
Contributor

AJIOB commented Nov 1, 2023

@JussiPekonen, do you have a required patches for the latest version?

@ensonic
Copy link

ensonic commented Feb 10, 2024

This or TAP would be quite nice. My motivation would be to allow github actions to report test results. I can open a new one for TAP format.

@AJIOB
Copy link
Contributor

AJIOB commented Feb 11, 2024

@ensonic, if you need JUnit XML output with timestamps support, you may use my repo with branch AJIOB/add-time-stamps, that stands in queue to create a PR (after the basic JUnit XML support adding).

@AJIOB
Copy link
Contributor

AJIOB commented Jun 21, 2024

Hi all,

Looks like we've merged the #176, so I think we can close this issue as completed.

Time measure support will be added by #180, but you can start using the current version.

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

No branches or pull requests

5 participants