Add an E2E test to test a regression on issue creation
Description of the test
This E2E test tests the fix for #299462 (closed) in which issues created from vulnerabilities and edited before submitting, the edits do not persist, the issue reverts to the original contents.
Testcase gitlab-org/quality/testcases#1228 (closed)
Check-list
-
Confirm the test has a [ testcase:
tag linking to an existing test case] (https://docs.gitlab.com/ee/development/testing_guide/end_to_end/best_practices.html#link-a-test-to-its-test-case-issue) in the test case project. - gitlab-org/quality/testcases#1228 (closed) -
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. -
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
Edited by Will Meek