-
Notifications
You must be signed in to change notification settings - Fork 0
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
Leverage the DryRun parameter in Pinpoint to emulate SMS sending #426
Comments
Changed code to
and get
So the sms is sent to AWS. After that it looks like it goes into the void. There are no delivery recipts. Question: does it cost us anything? Use the cli to send to myself with and without the 4:07 4:11 4:17 4:27 So looks like dry runs
I think we can safely switch the |
Use |
ugh, broke the smoke test when we stopped sending a delivery receipt for the test number. fix: |
Did the QA. Sent a text from my service to the dry run number. Verified that it did not actually send a text via the logs in Quicksight. Did a followup test with the same service -- sent to my personal number, and verified that it did indeed send it. Verified that AWS did indeed get both requests via the logs, but that only the non-dry run number actually was processed/sent. There were no logs for the dry run, which verifies that we didn't spend any money! QA -- COMPLETE! |
Description
As a tester of GCNotify,
I need to emulate SMS sending
So that I can achieve test the system properly without paying for the sending.
WHY are we building?
We need to emulate the SMS sending.
WHAT are we building?
Enable the
DryRun
parameter via pinpoint and trigger it on a pre-established mechanism (by service/template ID for example).VALUE created by our solution
Test our system without incurring charges.
Acceptance Criteria
QA Steps
The text was updated successfully, but these errors were encountered: