A question about Improve Integration Tests coverage

Community GSOC
1

I’m drafting my proposal for the “Integration Test Coverage” project. Looking at the current stats, I see low coverage in both Controller Classes (approx. 5.9%) and REST API Controllers (approx. 4.1%).

Could you please clarify whether the 60% coverage goal applies to both categories combined, or if there is a specific priority for REST API endpoints over legacy web controllers?

2

the 60% is for all categories !

2 Likes
3

Thanks for the reply

4 
Hi OpenELIS team,

I’ve opened a PR for PatientService integration test improvements:
https://github.com/DIGI-UW/OpenELIS-Global-2/pull/3206

What’s included:
- Expanded integration coverage in `PatientServiceTest`
- Added/updated tests for:
  - patient identity lookup by sample status + project
  - persist patient data flow (including contact creation)
  - patient address insertion helper path
  - FHIR UUID generation on insert
- Added focused DBUnit fixture data for the sample/project/patient identity query path

Validation:
- Ran targeted JUnit 4 tests for the new/updated scenarios
- Confirmed the previously failing patient identity test now passes

I’d really appreciate feedback on:
1) whether the DBUnit dataset scope looks appropriate,
2) whether these test cases cover the highest-risk service paths,
3) any additional edge cases you’d like included before merge.

Thanks for your time and review.
1 Like