Add mock data for additional scenarios #2
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.
Changes here mostly involve adding cases to
mock.pyfor the variety of scenarios that theui-claim-trackeraccounts for. I used this page to determine what content needed to be set for each scenario, and then I tested each of them out using ModHeader to trigger the different cases.In addition, I updated the readme to reflect the new possible values for the
uniqueNumber, and changedhasPendingWeekstohasValidPendingWeeksto match what the claim tracker expects.The number of cases has just about doubled with these changes, so if you'd prefer them to be broken down differently or put into helper functions or into other files, let me know and I can work that in too. Also feel free to just leave these out, and I'll keep working out of my fork for the purposes of demoing this, etc.