Add scenarios for different DiagnosticReports #958

adrianclay · 2024-10-21T20:20:16Z

What

Please include a summary of the changes and the related issue

Please include details of the reasoning for these changes

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Internal change (non-breaking change with no effect on the functionality affecting end users)
Breaking change (fix or feature that would cause existing functionality to not work as expected)

I have performed a self-review of my code
I have made corresponding changes to the documentation
My changes generate no new warnings
I have added tests that prove my fix is effective or that my feature works
New and existing unit tests pass locally with my changes
I have updated the Changelog with details of my change in the UNRELEASED section if this change will affect end users

github-actions · 2024-11-29T09:16:04Z

Looks good. No mutations were possible for these changes.
See https://pitest.org

sonarqubecloud · 2024-11-29T09:16:48Z

adrianclay force-pushed the investigations-wiremock branch 2 times, most recently from 106c062 to f6935fa Compare October 21, 2024 21:46

NHSDigital deleted a comment from github-actions bot Oct 21, 2024

adrianclay closed this Oct 22, 2024

adrianclay deleted the investigations-wiremock branch October 22, 2024 08:44

adrianclay restored the investigations-wiremock branch November 18, 2024 14:05

adrianclay reopened this Nov 18, 2024

adrianclay force-pushed the investigations-wiremock branch from f6935fa to 899845a Compare November 18, 2024 14:07

NHSDigital deleted a comment from github-actions bot Nov 18, 2024

Add scenarios for different DiagnosticReports

4f56eda

adrianclay force-pushed the investigations-wiremock branch from 899845a to 4f56eda Compare November 29, 2024 09:14