Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Defect/173 report coverage date overlap #427

Merged
merged 17 commits into from
Aug 4, 2022

Conversation

Elaine-Krauss-TCG
Copy link
Contributor

API Ticket 173

Updates the coverage date overlap checking to catch an edge case where a new report is created whose dates entirely encompass another report's dates. Adds unit tests to verify that the edge case has been caught.

@Elaine-Krauss-TCG
Copy link
Contributor Author

Shelly has pointed out that a comment on the ticket adds fixing the coverage date fields to the requirements. A fix for that has been added.

@sonarcloud
Copy link

sonarcloud bot commented Aug 4, 2022

SonarCloud Quality Gate failed.    Quality Gate failed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

75.9% 75.9% Coverage
0.0% 0.0% Duplication

@mjtravers mjtravers dismissed toddlees’s stale review August 4, 2022 16:21

Issue was resolved. No timing is used now

@mjtravers mjtravers merged commit 7777b74 into develop Aug 4, 2022
@mjtravers mjtravers deleted the defect/173-report-coverage-date-overlap branch August 4, 2022 16:21
@Elaine-Krauss-TCG Elaine-Krauss-TCG restored the defect/173-report-coverage-date-overlap branch August 4, 2022 16:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants