Should we have a nice report for the test runs on Github Actions? https://github.com/marketplace/actions/test-reporter or https://github.com/marketplace/actions/junit-report-action provides a ready to use action step for this
Yes, yes please!
Maybe I can make that part of my JUnit 5 transition PR?
(Which is underway BTW)
Sure or shall we create a smoke test PR (and issue) and put the reports there?
More tweaks necessary than I expected. Didn't have on my radar we'd have so many parameterized tests in JUnit4. The swiss folks were busy! And yet again I see why I prefer JUnit 5 to write those... Just so much more convenient!
Technically the unit tests have their own results which are not dependent on a smoke test. So I'd rather publish them as part of this testing.
Sounds good. That's how it used to be when I had chained Jenkins jobs set up. Only if the unit tests passed would it even advance to API tests. When all is passing you can see separate reports.
(I'll start a new topic someday about combined code coverage.)
In my PR for OIDC I introduce real integration tests for the first time
haha I was about to go there :smile_cat:
I'll stop blabbering now... :shush:
I just finished updating https://github.com/IQSS/dataverse/pull/9273 with latest develop. Extended docs on integration testing as well. JaCoCo working smoothless now :partying_face: @Philip Durbin should we address the reporting thing in this one?
Sure!
I created this related issue: Let contributors know why tests are failing #9916
Here's an example of MoveIT failing: https://jenkins.dataverse.org/job/IQSS-Dataverse-Develop-PR/view/change-requests/job/PR-9925/2/testReport/
Screen-Shot-2023-09-18-at-5.13.52-PM.png
Do we want reports always() or just on failure() @Philip Durbin ?
Hmm, can we please try always?
First progress: https://github.com/IQSS/dataverse/actions/runs/6228536081 shows an artifact with results from unit + integration testing
(not API!)
Great but from a private/incognito window I can't download the artifacts.
"The Actions API has just been released, and this can be used to retrieve an artifact download URL.
See https://developer.github.com/v3/actions/artifacts/ "
-- https://github.com/actions/upload-artifact/issues/27#issuecomment-578937784
Here, try this: https://nightly.link/IQSS/dataverse/workflows/maven_tests/9916-action-reports/junit-test-results.zip
Via Artifact download URL only work for registered users (404 for guests) #51 at https://github.com/actions/upload-artifact/issues/51
Just leaving this compare link to see the recent commits: https://github.com/poikilotherm/dataverse/compare/9268-mpconfig-oidc-provider...IQSS:dataverse:9916-action-reports
No no no, the point is that these reports can be used from another workflow in the repo context, which has write access to the run. Otherwise runs from forks will not have reports.
But I almost fell asleep before my keyboard, so I had to take a break after this step
Ok, but you have to admit that nightly.link is a neat hack. :big_smile:
Oh yes it is :-D
Last updated: Nov 01 2025 at 14:11 UTC