[Issue] Remove a duplicated <severity> tag from MFTF test AdminSetUpWatermarkForSwatchImageTest

[m2-assistant[bot]]

This issue is automatically created based on existing pull request: magento/magento2#31862: Remove a duplicated tag from MFTF test AdminSetUpWatermarkForSwatchImageTest

---

Description (*)

While looking at functional tests provided by Magento I found that one of the tests AdminSetUpWatermarkForSwatchImageTest has two severity tags with the same value = MAJOR. I think only one of them is needed.

Related Pull Requests

I cannot find which pull request added the second one but the commit is https://github.com/magento/magento2/commit/bba6a438c71045eef0083bfa3374065b26d9485d

The original commit that introduced the test and the first severity tag is https://github.com/magento/magento2/commit/9bea49f2e5e1b41c18aa4bf0b12510e083a5f1e4

Fixed Issues (if relevant)

No issue is created for this ticket.

Manual testing scenarios (*)

No manual tests are required. This is code refactoring.

Questions or comments

No questions or comments at this point.

Contribution checklist (*)

• [x] Pull request has a meaningful description of its purpose
• [x] All commits are accompanied by meaningful commit messages
• [x] All new or changed code is covered with unit/integration tests (if applicable)
• [x] All automated tests passed successfully (all builds are green)

[engcom-November]

Hello @denchev,

Thank you for the report and collaboration!

Verified on 2.4-develop. The severity tag is repeated twice in AdminSetUpWatermarkForSwatchImageTest test, hence confirmig the issue.

Thank you.

[m2-assistant[bot]]

Hi @engcom-November. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• [ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• [ ] 5. Add label Issue: Confirmed once verification is complete.
• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-11873 is successfully created for this GitHub issue.

[m2-assistant[bot]]

:white_check_mark: Confirmed by @engcom-November. Thank you for verifying the issue.
Issue Available: @engcom-November, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.