Bring in realistic data into staging

[jimleroyer]

Description

As a tester, I want to test GCNotify with realistic data similar to production in the staging environment, So that I can catch production errors early on before it gets released.

WHY are we building?

To catch errors earlier before it hits production. Replicating our staging env to be the same (or closer) to production has been an effort in the past, but not on the data side until now.

WHAT are we building?

Have realistic data in staging, but not real. Hence a mere production data dump in staging is not sufficient and might violate our policies. At the same time, we do want similarity for data between the two environments.

There are multiple ways on how to achieve such a goal but this issue description should not be prescriptive on how to do so.

VALUE created by our solution

The staging environment is closer to the production one and our testing in the former is much improved.

Acceptance Criteria

Given an issue that requires some complex data relationships and/or volume, when it gets triggered in the staging environment, then the testing in that environment is able to detect it.

• [ ] Generate appropriate log messages so that executions of this feature can be tracked
• [ ] Can misuse of this feature cause harm? If yes, create an alert
• [ ] Update the status of related findings, insights, and hypotheses on the Research Airtable
• [ ] Once change/fix/feature is implemented, link relevant Airtable records to design artifacts (Figma)

Privacy considerations

No production data in staging environment.

Security controls in place

TBD.

Measuring success and metrics

• Data relationships scoring.
• Volume data

QA Steps

• [ ] TBD

[jimleroyer]

App team opened a potential duplicate with #1533.