E2E test Alerts setting for http endpoint integration
Description of the test
New E2E test for Category:Incident Management grouprespond - HTTP endpoint integration can send test alert that creates new alert
Test case: https://gitlab.com/gitlab-org/gitlab/-/quality/test_cases/382803
Related to #381381 (closed)
Note: I'm going to defer feature's specific behaviors to feature test proposals here #382266
How to set up and validate locally
Follow steps provided in test case https://gitlab.com/gitlab-org/gitlab/-/quality/test_cases/382803
OR in gitlab/qa/
execute command to run test against GDK
$ QA_GITLAB_URL=http://<local.ip.address>:3000 bundle exec rspec qa/specs/features/browser_ui/8_monitor/incident_management/basic_alerts_single_http_integration_spec.rb
Checklist
-
Confirm the test has a testcase:
tag linking to an existing test case in the test case project. -
Note if the test is intended to run in specific scenarios. If a scenario is new, add a link to the MR that adds the new scenario. -
Follow the end-to-end tests style guide and best practices. -
Use the appropriate RSpec metadata tag(s). - Most resources will be cleaned up via the general cleanup task. Check that is successful, or ensure resources are cleaned up in the test:
-
New resources have api_get_path
andapi_delete_path
implemented if possible. -
If any resource cannot be deleted in the general delete task, make sure it is ignored. -
If any resource cannot be deleted in the general delete task, remove it in the test (e.g., in an after
block).
-
-
Ensure that no transient bugs are hidden accidentally due to the usage of waits
andreloads
. -
Verify the tags to ensure it runs on the desired test environments. -
If this MR has a dependency on another MR, such as a GitLab QA MR, specify the order in which the MRs should be merged. -
(If applicable) Create a follow-up issue to document the special setup necessary to run the test: ISSUE_LINK -
If the test requires an admin's personal access token, ensure that the test passes on your local environment with and without the GITLAB_QA_ADMIN_ACCESS_TOKEN
provided.
Edited by Tiffany Rea