Skip to content

Update module-wise code coverage telemetry in 1es#5380

Merged
rbans96 merged 5 commits intomainfrom
personal/ribans/fix-modulename
Feb 17, 2026
Merged

Update module-wise code coverage telemetry in 1es#5380
rbans96 merged 5 commits intomainfrom
personal/ribans/fix-modulename

Conversation

@rbans96
Copy link
Contributor

@rbans96 rbans96 commented Feb 10, 2026

Description

In the 1es telemetry tables, code coverage telemetry was present per class and not per module. Updated to get the telemetry per module.
PublishCodeCoverageResults@2 receiving Cobertura XML stored data per-class without module/assembly names in the CodeCoverageModule table. The fix is to feed it native .coverage binary files instead, which contain proper assembly-level information.

Related issues

Addresses 182694

Testing

Describe how this change was tested.

FHIR Team Checklist

  • Update the title of the PR to be succinct and less than 65 characters
  • Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
  • Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
  • Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
  • Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
  • When changing or adding behavior, if your code modifies the system design or changes design assumptions, please create and include an ADR.
  • CI is green before merge Build Status
  • Review squash-merge requirements

Semver Change (docs)

Patch|Skip|Feature|Breaking (reason)

@rbans96 rbans96 added this to the CY25Q3/2Wk07 milestone Feb 10, 2026
@rbans96 rbans96 requested a review from a team as a code owner February 10, 2026 19:05
@rbans96 rbans96 added Enhancement-Test Enhancement on tests. Azure API for FHIR Label denotes that the issue or PR is relevant to the Azure API for FHIR Azure Healthcare APIs Label denotes that the issue or PR is relevant to the FHIR service in the Azure Healthcare APIs No-PaaS-breaking-change No-ADR ADR not needed labels Feb 10, 2026
@rbans96 rbans96 changed the title Fix module name for code coverage telemetry [Draft] Fix module name for code coverage telemetry Feb 11, 2026
@rbans96
Copy link
Contributor Author

rbans96 commented Feb 11, 2026

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@rbans96
Copy link
Contributor Author

rbans96 commented Feb 13, 2026

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@rbans96
Copy link
Contributor Author

rbans96 commented Feb 13, 2026

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@rbans96 rbans96 changed the title [Draft] Fix module name for code coverage telemetry Update module-wise code coverage telemetry in 1es Feb 17, 2026
@rbans96 rbans96 merged commit d96b2eb into main Feb 17, 2026
64 checks passed
@rbans96 rbans96 deleted the personal/ribans/fix-modulename branch February 17, 2026 17:53
rbans96 added a commit that referenced this pull request Feb 19, 2026
rbans96 added a commit that referenced this pull request Feb 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Azure API for FHIR Label denotes that the issue or PR is relevant to the Azure API for FHIR Azure Healthcare APIs Label denotes that the issue or PR is relevant to the FHIR service in the Azure Healthcare APIs Enhancement-Test Enhancement on tests. No-ADR ADR not needed No-PaaS-breaking-change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants