Attempt to handle FY boundaries in utilization tests #1368
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The utilization tests in
tock/utilization/tests/test_views.py
seem to get tripped up when the fiscal year changes for the first 7 to 10 days of October. The original behavior was to create aReportingPeriod
that had a start date of today minus 7 days. If today's date is in early October and you rewind 7 days back into late September, the resulting reporting period spans two fiscal years.This attempts to address the issue by checking if "today" is far enough into October that rewinding 7 days would leave the reporting period in the current fiscal year and not cause issues 🤞
@Jkrzy - Thanks for the mountain of help in figuring out the problem and solution.