-
Notifications
You must be signed in to change notification settings - Fork 17
feat(OP-2576): Add bulk synthetic data generator command #400
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
base: develop
Are you sure you want to change the base?
feat(OP-2576): Add bulk synthetic data generator command #400
Conversation
|
init.py was missing under command & leaf folder as well. |
|
@sunilparajuli please also consider reusing or deleting this: https://github.com/openimis/openimis-be-insuree_py/blob/develop/insuree/management/commands/generateinsurees.py |
…ch and added faker
I will consider carefully removing this in next PR |
| from insuree.models import (ConfirmationType, Education, Family, FamilyType, | ||
| Gender, IdentificationType, Insuree, InsureePolicy, | ||
| Profession, Relation, InsureeStatus) | ||
| from location.models import HealthFacility, Location | ||
| from medical.models import Diagnosis, Item, Service | ||
| from policy.models import Policy | ||
| from product.models import Product |
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.
Would these cause circular dependency issues? Should this script be moved to medical/claim/assembly module?
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.
yes this could raise circular dependency as of now, to avoid i can move it to the functions below but i agree it should be moved to medical/claim module. I will move it to claim or medical which seems most fit.
Summary
Create Django management command to generate bulk synthetic test data for insurees, families, policies, and claims for performance testing and development environments.
Background
Currently, we lack sufficient test data to properly evaluate system performance under realistic load conditions. Manual data entry is time-consuming and doesn't scale for performance testing scenarios where we need thousands of records.
Usage Examples