Skip to content
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

Closed
joeyorlando opened this issue Jul 31, 2023 · 3 comments · Fixed by #3114
Closed

Uncomment out/finish e2e test for SMS verification/alert notification workflow #2693

joeyorlando opened this issue Jul 31, 2023 · 3 comments · Fixed by #3114
Assignees

Comments

@joeyorlando
Copy link
Contributor

joeyorlando commented Jul 31, 2023

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:

  • verifies a phone number for the test user
  • adds SMS notifications to the user's personal notification policy
  • sends a demo alert and asserts that the user receives the SMS

Deliverables

  • re-activate this test. Configure CI to contain the necessary environment variables to be able to successfully run this test. Note: you will also need to add these same environment variables to oncall-private
  • also, we should only run this particular test on commits to dev and/or master. 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

@github-actions
Copy link
Contributor

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 😄!

@joeyorlando
Copy link
Contributor Author

Note to whomever takes this issue. There is already a MAILSLURP_API_KEY repository secret. However, it is old and should be overwritten with a new API key once IT finishes setting up the MailSlurp account.

@joeyorlando
Copy link
Contributor Author

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.

joeyorlando added a commit that referenced this issue Oct 4, 2023
# 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
brojd pushed a commit that referenced this issue Sep 18, 2024
# 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant