-
Notifications
You must be signed in to change notification settings - Fork 299
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
Uncomment out/finish e2e test for SMS verification/alert notification workflow #2693
Comments
The current version of Grafana OnCall, at the time this issue was opened, is v1.3.19. If your issue pertains to an older version of Grafana OnCall, please be sure to list it in the PR description. Thank you 😄! |
Note to whomever takes this issue. There is already a |
got access from procurement, however there now seems to be an issue when upgrading the plan in MailSlurp. I've sent a support request to the MailSlurp team, will move this to blocked until I hear back from them. |
# What this PR does Since we now have a Mailslurp account we can start running this test. At the moment it is only run 1x daily on a GitHub Actions cron (to avoid incurring costs; [it is skipped](https://github.com/grafana/oncall/blob/dev/.github/workflows/linting-and-tests.yml#L317) via a Playwright "[test annotation filter](https://github.com/grafana/oncall/blob/dev/grafana-plugin/package.json#L14-L15)"). `MAILSLURP_API_KEY` repo secret has already been updated. Closes #2693
# What this PR does Since we now have a Mailslurp account we can start running this test. At the moment it is only run 1x daily on a GitHub Actions cron (to avoid incurring costs; [it is skipped](https://github.com/grafana/oncall/blob/dev/.github/workflows/linting-and-tests.yml#L317) via a Playwright "[test annotation filter](https://github.com/grafana/oncall/blob/dev/grafana-plugin/package.json#L14-L15)"). `MAILSLURP_API_KEY` repo secret has already been updated. Closes #2693
What would you like to see!
We have (unfortunately) broken this workflow a few times. This results in issues like #2687 as well as customer escalations.
There is already an e2e test which does the following:
Deliverables
oncall-private
dev
and/ormaster
. avoid running it on every feature branch commit as Mailslurp has a "pay as you go" model for inbound SMSes. See the Playwright docs on "Tagging tests" for how to get started on conditionally running tests like this.Product Area
Alert Flow & Configuration
Anything else to add?
No response
The text was updated successfully, but these errors were encountered: