Let's talk about code coverage.
https://github.com/IQSS/dataverse-frontend shows 97%, which is awesome:
![]()
https://github.com/IQSS/dataverse shows 26% for unit tests and "inaccessible" for API tests:
![]()
I have had trouble getting JaCoCo reports out of the Integration Test runners.
At the time, it was turning into a blocker, so I put it aside, but let me take another crack at it
Oliver said he was able to do it for some other workflows
Right. We probably talked about it during the move from Jenkins to GitHub Actions. I'm glad we didn't let this be a blocker. But we should revisit some day, yes.
The backend README has those broken links to Jenkins. Do you think we should just remove them for now?
Yep, we should. Jenkins has been turned off
Ok. I created an issue: The README has broken links to Jenkins, now defunct #12784
#12783 addresses code coverage now. I am looking into reactivating the badges
Here's what it fixes:
Each browser job also runs the full API test suite against the same installation, so every commit gets three independent runs of the API tests under real UI load, which is good for catching flaky tests.
Push to green: ~50 → ~42 min. The tests themselves are unchanged.
Current code coverage after #12783 is looking at about 57% on Coveralls
https://coveralls.io/jobs/189690986
57%! That's what I'm talking about!
And at https://coveralls.io/jobs/189690986/source_files/12682577818 for example I can see which lines in /src/main/java/edu/harvard/iq/dataverse/api/Datasets.java (part of the API) are green/covered or red/uncovered. Great!
![]()
Last updated: Nov 02 2026 at 07:01 UTC