You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that the generated (junit) test reports are not being picked up bu Jenkins's junit plugin.
We think it's due to the classname attribute being empty string. One solution could be to omit this attribute altogether. From the plugin's source code it should then pick up the suite's name (which would be ok in this case).
An example file we have is:
<?xml version='1.0' encoding='UTF-8'?><testsuitehostname=""name="Consumer-Provider"tests="1"errors="0"failures="0"time="1.540066584878778E12">
<properties></properties><testcaseclassname=""name="Fetch a complete payload"time="0.0"></testcase><system-out></system-out>
<system-err></system-err>
</testsuite>
The text was updated successfully, but these errors were encountered:
I believe you, I'm slightly shocked that no-one has ever reported that before.
Could I interest you in trying your fix and submitting a PR? If you changed the version to be the right one and than run bash scripts/localpublish.sh from the repo's root it will ...er.. locally publish Scala-Pact, as you'd expect. You could then copy the artefacts into Jenkins' ivy cache and try it again?
Otherwise you'll have to wait for me to fix it, which I will, but I can't promise when....
It seems that the generated (junit) test reports are not being picked up bu Jenkins's junit plugin.
We think it's due to the
classname
attribute being empty string. One solution could be to omit this attribute altogether. From the plugin's source code it should then pick up the suite's name (which would be ok in this case).An example file we have is:
The text was updated successfully, but these errors were encountered: