This is a guide for creating a feature that will involve email sending to the users of an app.
As for protective measures, to prevent the app from sending unnecessary emails to users. All new functions or updated functions of PR related to the email-sending feature need to be sent out manually, and this should be done 3 times before we schedule them to automatically send these emails to users.
Steps when testing and sending the emails:
Tester/s need to test the functionality via the generated CSV report, ideally in the morning. Then Av needs to send them around 4:00 in the afternoon if all goes well with the testing.
All massive information email-sending modules need to have a function for testing and provide the tester easy access to the test results. (in the case of Scaling, there's a feature to generate a CSV report to verify the users that will receive the emails)
Use the current email sending function as an example:
- Tester can trigger the test API to acquire an email that consists of:
- Top Deals: Receiver list(who) & Content list(what).
- Deal Report: Receiver list(who) & Content list(what).
- All of those kind of the APIs must requires a secret token to access.