We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, if a wft4galaxy test suite is run, it would be great if there was a human readable output. Maybe akin to https://wiki.jenkins-ci.org/display/JENKINS/Test+Results+Analyzer+Plugin . There seem to be also some hints here: http://stackoverflow.com/questions/8079071/xml-format-specification-dtd-xsd-for-unit-test-reports Yours, Steffen
The text was updated successfully, but these errors were encountered:
Currently the output is generated by Python's unittest.TextTestRunner, though it can get messy if the options --debug or --enable-logger are used.
unittest.TextTestRunner
--debug
--enable-logger
Providing a graphical report could be done by implementing a new component and refactoring the existing wft4galaxy script.
wft4galaxy
Sorry, something went wrong.
Merge pull request #1 from ilveroluca/feature/support-xunit-output-fo…
9097cd1
…rmat Change `--xunit` argument to more generic `--output-format xunit`
No branches or pull requests
Hi, if a wft4galaxy test suite is run, it would be great
if there was a human readable output. Maybe akin to https://wiki.jenkins-ci.org/display/JENKINS/Test+Results+Analyzer+Plugin . There seem to be also some hints here: http://stackoverflow.com/questions/8079071/xml-format-specification-dtd-xsd-for-unit-test-reports
Yours, Steffen
The text was updated successfully, but these errors were encountered: