-
Notifications
You must be signed in to change notification settings - Fork 4
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
Feat/2965 db seed impl #3134
Feat/2965 db seed impl #3134
Conversation
def handle(self, *args, **options): | ||
"""Populate datafiles, records, summaries, and errors for all STTs.""" | ||
|
||
for stt in STT.objects.all(): # filter(id__in=range(1,2)): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think all
might be excessive here, might take in an argument that utilizes the range in the comment to have a more limited subset of STTs.
# https://faker.readthedocs.io/en/stable/providers/baseprovider.html#faker.providers.BaseProvider | ||
""" class FieldFaker(faker.providers.BaseProvider):...""" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should probably delete this, but wanted to leave myself this breadcrumb.
|
||
# iterate over models and generate lines | ||
for _, model in models_in_section.items(): | ||
if long_section in ['Active Case Data', 'Closed Case Data', 'Aggregate Data', 'Stratum Data']: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is SSP covered with this too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, it definitely wouldn't. I'll get that fixed up
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR led me to find a very small but impactful error in another area of our parser code that causes this db seed implementation to generate zero valid records when the fix for the error is added. It's a bit verbose to explain here so I will bring it up today on OH and we can document it that way.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #3134 +/- ##
========================================
Coverage 92.66% 92.66%
========================================
Files 47 47
Lines 1009 1009
Branches 169 169
========================================
Hits 935 935
Misses 42 42
Partials 32 32
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report in Codecov by Sentry.
|
|
|
@andrew-jameson Ya I think it makes sense to discuss/fix the cat4 bug in a separate ticket and leave the case consistent DB seed work as the ticket you linked. |
Summary of Changes
Pull request closes #2965
How to Test
TANF-app/tdrs-backend/tdrs_db_seed.pg
Deliverables
More details on how deliverables herein are assessed included here.
Deliverable 1: Accepted Features
Checklist of ACs:
lfrohlich
and/oradpennington
confirmed that ACs are met.Deliverable 2: Tested Code
CodeCov Report
comment in PR)CodeCov Report
comment in PR)Deliverable 3: Properly Styled Code
Deliverable 4: Accessible
iamjolly
andttran-hub
using Accessibility Insights reveal any errors introduced in this PR?Deliverable 5: Deployed
Deliverable 6: Documented
Deliverable 7: Secure
Deliverable 8: User Research
Research product(s) clearly articulate(s):