Details
Details
Not really sure what is the best way to test it - maybe @will have some ideas.
On APNs:
- Notif works
- Update the code to send notif with random priority -> fails with BadPriority
On web:
- Notif works
- Triggering error is complicated because we use lib, so just reading the code as we use the same approach as for others
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Branch
- secondary-auth
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
services/tunnelbroker/src/websockets/session.rs | ||
---|---|---|
667–673 | there is no better place to do it, for Web Push we use lib instead of our custom implementation |
Comment Actions
Testing that adding WEB_PUSH_ERROR and APNS_ERROR error types to an error log will trigger an alarm + email notif has already been tested. I don't think this needs further testing.
The best way of testing this would be to ensure that failing to sending APNs error or Web Push notif logs the error. Cloudwatch alarms will take care of the rest
Doing this locally and ensuring you can find the error logs should be sufficient imo