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

[Obs Alerting] API integration test coverage for Obs Alerting API usage #187078

Closed
jasonrhodes opened this issue Jun 27, 2024 · 2 comments
Closed
Labels
Team:obs-ux-management Observability Management User Experience Team

Comments

@jasonrhodes
Copy link
Member

We need to confirm we have adequate test coverage for Observability Alerting API integration tests. I expect this means both incoming (e.g. creation of our various rule types are well tested) and outgoing (we have tests that assert against the way we interact with any ES APIs or Kibana APIs such as saved objects, etc). It's possible that the platform response ops tests already cover these cases for us and we can close this without adding our own tests, but we may want a few that test specifics of our own rule types, too. Let's discuss.

Please feel free to refine/add detail to this issue description. The A/C is to identify any missing test coverage in this area and either create the needed tests or create issues to make sure these tests are created before GA.

@jasonrhodes jasonrhodes added the Team:obs-ux-management Observability Management User Experience Team label Jun 27, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)

@jasonrhodes
Copy link
Member Author

Closing this in favor of individual issues outlined in this meta --- #183263

@jasonrhodes jasonrhodes reopened this Oct 15, 2024
@jasonrhodes jasonrhodes closed this as not planned Won't fix, can't repro, duplicate, stale Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:obs-ux-management Observability Management User Experience Team
Projects
None yet
Development

No branches or pull requests

2 participants