-
Notifications
You must be signed in to change notification settings - Fork 37
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
Add Mailosaur to tests #16
Comments
Will not work when testing locally and also not on our testing site, because of the k8s setup. Needs to use a different solution than our current testing setup. |
Another interesting solution might be mailhog - it has an api and you can host it locally in a docker container. |
@kolaente yes we use that locally and that works fine, but when running the tests in a CI/CD situation it's limited. Using Mailosaur will enable us to inspect the emails later when something went wrong. |
@peterjaap , I currently try to set up our CI/CD integration for the tests. |
@norgeindian I haven't run in that yet, maybe because we generally use |
@peterjaap , thanks for this amazingly fast reply. |
For some tests like reset password nieuws, newsletter subscription, order confirmation etc mails need te be received and read. For this purpose Mailosaur can be used. A mailosaur API-key and account will be needed, the API-key needs to be added to the
cypress.json
"env" object or to acypress.env.json
file. And the serverId needs to be added to the tests where mailosaur is used.Tests
Example:
The text was updated successfully, but these errors were encountered: