Skip to content

Add tests for new MR from push notification

Mark Lapierre requested to merge ml-add-new-tests-mr-from-push-notification into master

Description of the test

Test that we can create an MR from the push event notification that looks like:

image

In a previous test that notification sometimes didn't appear, so I made that test create an MR via an alternative method: !85659 (merged)

These two new tests make sure that notification still appears when it is supposed to. It's possible the test will fail under the conditions of the previous test.

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).
  • Ensure that a created resource is removed after test execution. A Group resource can be shared between multiple tests. Do not remove it unless it has a unique path. Note that we have a cleanup job that periodically removes groups under gitlab-qa-sandbox-group.
  • Ensure that no transient bugs are hidden accidentally due to the usage of waits and reloads.
  • 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 Mark Lapierre

Merge request reports