MFTF: Test isolation, consistent naming (backwards-compatible)

[lbajsarowicz]

Description (*)

Currently when you run vendor/bin/mftf run:test -r StorefrontResetCustomerPasswordSuccessTest StorefrontResetCustomerPasswordFailedTest, as a result second test will fail. This is because of lack of isolation between these tests.

Conditions that should be fulfilled are:

1. IP Address should not affect the results of tests
2. Each of tests should "clean up" after itself.

Also renamed one of the tests to be consistent, replaced manual actions with Action Groups.
Old name was moved to the _Deprecated_Test.xml that is still available for those who extend old test, with deprecated annotation.

Related Pull Requests

Fixed Issues (if relevant)

N/A

Manual testing scenarios (*)

1. Execute functional tests

Questions or comments

CC: @okolesnyk

Contribution checklist (*)

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

[m2-assistant]

Hi @lbajsarowicz. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Guide documentation.

[magento-engcom-team]

Hi @dmytro-ch, thank you for the review.
ENGCOM-7092 has been created to process this Pull Request

[engcom-Alfa]

✔️ QA passed

[engcom-Charlie]

Failed functional tests not related to the changes in this PR.

[m2-assistant]

Hi @lbajsarowicz, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.