[Issue] [MFTF] Refactoring of AdminMassOrdersCancelCompleteAndClosedTest

[m2-assistant]

This issue is automatically created based on existing pull request: #31123: [MFTF] Refactoring of AdminMassOrdersCancelCompleteAndClosedTest

---

Description (*)

A new test has been created according to the best practices followed by MFTF.
The old "AdminMassOrdersCancelCompleteAndClosedTest" has been deprecated.

Manual testing scenarios (*)

1. Create two orders
2. Invoice and ship the first order
3. Invoice and refund the second order
4. Go to the Orders Grid
5. Try to cancel both orders via mass update
6. Verify the result

[m2-assistant]

Hi @engcom-Delta. 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: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components 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.

[magento-engcom-team]

✅ Confirmed by @engcom-Delta
Thank you for verifying the issue. Based on the provided information internal tickets MC-39904 were created

Issue Available: @engcom-Delta, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[magento-engcom-team]

Hi @m2-assistant[bot]. Thank you for your report.
The issue has been fixed in #31123 by @AnnaAPak in 2.4-develop branch
Related commit(s):

• 9847f03d47e5027c7f27c4e5c800896a5b199582
• e34fc7826d04dcd7e504082d5fa0d7f029343225
• beb0fda08417c7dfec5063a1335639cb356cd9f2
• 320748f555d4036d50ed83ebb32a81972aa29579
• d2ab2f389d64d349dca0ddc3246654c94c806cc3
• 7dcd88bd75b83a0a7016b36738462a2e256d8d20
• 732c6ff48720740fa0e399f2b1d85b198dd41c9e
• a70dfc91c5842aa8ae497912ac91ca2ca93f5020
• a5dd5e99039e17705a42297b14a9a40fcd11d96f
• 424754fe4bc2acec733f6bc9736afde5232553c7
• 035442d47019e7a82bc193787adce2086032f3a5
• aaea37c20a2e882fec898a6c484ed0c69e3fad46
• bc231ce31a22b9f8120d1a9542a066cbc61ba70a
• de26beff5cad54cf4538ee617d68cf7a39ee5892

The fix will be available with the upcoming 2.4.3 release.