The test-open-data-assets workflow fails basically every time due to a quirk in our data upload schedule: We only update historical (prior year) values once a year, and we only update the most recent year each month, but we test all years every month. This means that historical years will continue to fail throughout the year as our staff make small edits to historical years (example).
Two options we have for handling this:
- Change historical tests to a percentage threshold (e.g. within 5% different instead of exactly matching)
- Only test historical values once per year, when we update them
Or maybe a combination of these two approaches.
The
test-open-data-assetsworkflow fails basically every time due to a quirk in our data upload schedule: We only update historical (prior year) values once a year, and we only update the most recent year each month, but we test all years every month. This means that historical years will continue to fail throughout the year as our staff make small edits to historical years (example).Two options we have for handling this:
Or maybe a combination of these two approaches.