Testing

[HarryET]

Ensure that all Echo Server routes work before we merge PRs, this can be done by updating the rust functional tests. Below is a list of endpoints that need to be tested. We also then need integration tests to ensure that staging works fully before deploying to prod, we could then also run these tests against prod to flag any issues before customers notice

This could be made easier by #89 as then we can just enable the multi-tenancy endpoints when building/testing for multi-tenancy and not when we are just testing self-hosted, this would also aid #66

We also then need to test specific parts of the logic so that we ensure everything works, there is a section below which also documents what parts should have some form of tests.

As a whole this issue will cause some refactors to the codebase to make it more re-useable as well as more testable

Endpoints

Preview Give feedback

1. GET /health
2. POST /clients
3. DELETE /clients/:id
4. POST /clients/:id (encrypted)
5. POST /clients/:id (json blob)
6. POST /tenants
7. GET /tenants
8. DELETE /tenants/:id
9. POST /tenants/:id/apns
10. POST /tenants/:id/fcm
11. POST /:tenant_id/clients
12. DELETE /:tenant_id/clients/:id
13. POST /:tenant_id/clients/:id (encrypted)
14. POST /:tenant_id/clients/:id (json blob)

Use Cases

• Single Tenancy
• Multi Tenancy

Logic

• Blob decoding
• Config (loading from env)
• Fetching/creating push provider
  • FCM
  • APNS
  • APNS Sandbox
• Validating signatures
• Fetching relay public key
• Stores
  • Client
  • Notification
  • Tenants