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

Add test for alerts/notifications to test the snuba pipeline #1887

Closed
Tracked by #1761
emmatyping opened this issue Dec 28, 2022 · 2 comments
Closed
Tracked by #1761

Add test for alerts/notifications to test the snuba pipeline #1887

emmatyping opened this issue Dec 28, 2022 · 2 comments
Assignees

Comments

@emmatyping
Copy link
Contributor

This is part of #1761, should hopefully better test snuba.

@emmatyping
Copy link
Contributor Author

We were advised that creating an alert would be a good way to test the snuba pipeline, however it seems that alert creation is a frontend only affair. The integration tests keep a cookie fresh, so perhaps the endpoint used by the frontend could still be used?

I'm also not sure how to handle alert firing, by default an email will be sent, I suppose we can check the server logs that happens.

@emmatyping
Copy link
Contributor Author

I have been trying out playwright, with the idea that it could make testing alerts easier since the alert interface is rather UI focused. Unfortunately, it seems that the front end for Sentry does not have node identifiers, which makes playwright hard to integrate... back to curl/jq I suppose... :/

@chadwhitacre chadwhitacre closed this as not planned Won't fix, can't repro, duplicate, stale Feb 6, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Feb 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants